X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4EF525E46C5 for ; Mon, 16 Aug 2004 13:23:13 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 54401-10 for ; Mon, 16 Aug 2004 16:22:53 +0000 (GMT) Received: from ucsns.ucs.co.za (ucs.co.za [196.23.43.2]) by svr1.postgresql.org (Postfix) with ESMTP id 22A115E46C4 for ; Mon, 16 Aug 2004 13:22:44 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by ucsns.ucs.co.za (Postfix) with ESMTP id 9788B2BD48; Mon, 16 Aug 2004 18:22:50 +0200 (SAST) Received: from ucsns.ucs.co.za ([127.0.0.1]) by localhost (ucsns.ucs.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29369-05; Mon, 16 Aug 2004 18:22:40 +0200 (SAST) Received: from ucspost.ucs.co.za (mailgw1.ucs.co.za [196.23.43.253]) by ucsns.ucs.co.za (Postfix) with ESMTP id 61A2B2BD43; Mon, 16 Aug 2004 18:22:40 +0200 (SAST) Received: from jhb.ucs.co.za (jhb.ucs.co.za [172.31.1.3]) by ucspost.ucs.co.za (Postfix) with ESMTP id 226D7D9DFB; Mon, 16 Aug 2004 18:22:40 +0200 (SAST) Received: from svb.ucs.co.za (svb.ucs.co.za [172.31.1.148]) by jhb.ucs.co.za (Postfix) with SMTP id A601E975A0; Mon, 16 Aug 2004 18:22:39 +0200 (SAST) Date: Mon, 16 Aug 2004 18:23:14 +0200 From: Stef To: pgsql-performance@postgresql.org Cc: Tom Lane Subject: Re: Strange problems with more memory. Message-Id: <20040816182314.24818138@svb.ucs.co.za> In-Reply-To: <14009.1092670876@sss.pgh.pa.us> References: <20040816171234.5a9bac8f@svb.ucs.co.za> <14009.1092670876@sss.pgh.pa.us> X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-pc-linux-gnu) User-Agent: sillypheed-claws (anti-aliased) X-Face: GFoC95e6r)_TTG>n~=uFLojP=O~4W@Ms]>:.DMm/')(z3\Mwj^XP@? Q:3";lD.OM1"^mDu}2NJ@US:)dO:U*iY5EM50&Tx. X-Operating-System: sid X-X-X: _-^-_ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at ucs.co.za X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/248 X-Sequence-Number: 7884 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