From: | Stef <svb(at)ucs(dot)co(dot)za> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Strange problems with more memory. |
Date: | 2004-08-16 16:23:14 |
Message-ID: | 20040816182314.24818138@svb.ucs.co.za |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-08-16 23:09:13 | Re: Timestamp-based indexing |
Previous Message | Tom Lane | 2004-08-16 15:41:16 | Re: Strange problems with more memory. |