Re: [PERFORM] Strange problems with more memory.

2004-08-16 Thread Mark Kirkwood
If your nightly process is heavily read-only, then raid5 is probably fine. If however, there is a significant write component then it would perhaps be worth getting another disk and converting to raid10 (alternatively - see previous postings about raid cards with on-board cache). Are you seeing

Re: [PERFORM] Strange problems with more memory.

2004-08-16 Thread Stef
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, b

Re: [PERFORM] Strange problems with more memory.

2004-08-16 Thread Tom Lane
Stef <[EMAIL PROTECTED]> writes: > It seems I was mistaking, as I started getting these kind of errors in dmesg : > VM: killing process postmaster > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) > __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) > VM: killing process postmaster This

[PERFORM] Strange problems with more memory.

2004-08-16 Thread Stef
Hi all, I'm running postgres 7.3.4 on a quad Xeon 2.8 GHz with Mem: 1057824768 309108736 7487160320 12242944 256413696 Swap: 518053888 8630272 509423616 on Linux version 2.4.26-custom Data directory is mounted with noatime. Nothing else but one 11GB database is running on this mach