pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stef <svb@ucs.co.za>
To: pgsql-performance@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Strange problems with more memory.
Date: Mon, 16 Aug 2004 18:23:14 +0200
Message-ID: <20040816182314.24818138@svb.ucs.co.za> (raw)
In-Reply-To: <14009.1092670876@sss.pgh.pa.us>
References: <20040816171234.5a9bac8f@svb.ucs.co.za>
	<14009.1092670876@sss.pgh.pa.us>

Tom Lane mentioned :
=> Turn off
=> memory overallocation in your kernel to get more stable behavior when
=> pushing the limits of available memory.

I think this will already help a lot.
Thanks!!

=> If your concern is with a single nightly process, then that quad Xeon is
=> doing squat for you, because only one of the processors will be working.
=> See if you can divide up the processing into several jobs that can run
=> in parallel.  (Of course, if the real problem is that you are disk I/O
=> bound, nothing will help except better disk hardware.  Way too many
=> people think they should buy a super-fast CPU and attach it to
=> consumer-grade IDE disks.  For database work you're usually better off
=> spending your money on good disks...)

Got 3 10000 rpm SCSI raid5 on here. I doubt I will get much better than that
without losing both arms and legs... 

I think I'll try and even out the disk IO a bit and get 4 processes running in parallel.
At least I can move forward again.

Thanks again!

Kind Regards
Stefan



view thread (4+ messages)  latest in thread

Message-ID: <20040816182314.24818138@svb.ucs.co.za>
Permalink:  ../20040816182314.24818138@svb.ucs.co.za/
Also on:    postgresql.org/message-id/20040816182314.24818138@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, tgl@sss.pgh.pa.us
  Subject: Re: Strange problems with more memory.
  In-Reply-To: <20040816182314.24818138@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