pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stef <svb@ucs.co.za>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres low end processing.
Date: Mon, 6 Oct 2003 09:55:51 +0200
Message-ID: <20031006095551.1d7bfeb8.svb@ucs.co.za> (raw)
In-Reply-To: <200310031108.49002.josh@agliodbs.com>
References: <20031003163040.3641f39a.svb@ucs.co.za>
	<200310031108.49002.josh@agliodbs.com>

Thanks for the replies,

On Fri, 3 Oct 2003 11:08:48 -0700
Josh Berkus <josh@agliodbs.com> wrote:
=> 1. Make sure that the WAL files (pg_xlog) are on a seperate disk from the 
=> database files, either through mounting or symlinking.
 
I'm not sure I understand how this helps?

=> 2. Tweak the .conf file for low vacuum_mem (1024?), but vacuum very 
=> frequently, like every 1-5 minutes.  Spend some time tuning your 
=> fsm_max_pages to the ideal level so that you're not allocating any extra 
=> memory to the FSM.
=>
=> 3. If your concern is *average* CPU/RAM consumption, and not peak load 
=> activity, increase wal_files and checkpoint_segments to do more efficient 
=> batch processing of pending updates as the cost of some disk space.  If peak 
=> load activity is a problem, don't do this.
=> 
=> 4. Tune all of your queries carefully to avoid anything requiring a 
=> RAM-intensive merge join or CPU-eating calculated expression hash join, or 
=> similar computation-or-RAM-intensive operations.

Thanks, I'll try some of these, and post the results.
The actual machines seem to be Pentium I machines,
with 32M RAM. I've gathered that it is theoretically 
possible, so no to go try it.

Regards
Stef

view thread (17+ messages)  latest in thread

Message-ID: <20031006095551.1d7bfeb8.svb@ucs.co.za>
Permalink:  ../20031006095551.1d7bfeb8.svb@ucs.co.za/
Also on:    postgresql.org/message-id/20031006095551.1d7bfeb8.svb@ucs.co.za

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: svb@ucs.co.za, josh@agliodbs.com
  Subject: Re: Postgres low end processing.
  In-Reply-To: <20031006095551.1d7bfeb8.svb@ucs.co.za>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox