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 8910F5E3F15 for ; Tue, 17 Aug 2004 03:24:14 -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 23535-02 for ; Tue, 17 Aug 2004 06:24:04 +0000 (GMT) Received: from linda-2.paradise.net.nz (bm-2a.paradise.net.nz [202.0.58.21]) by svr1.postgresql.org (Postfix) with ESMTP id 523DE5E3633 for ; Tue, 17 Aug 2004 03:24:00 -0300 (ADT) Received: from smtp-2.paradise.net.nz (smtp-2a.paradise.net.nz [202.0.32.195]) by linda-2.paradise.net.nz (Paradise.net.nz) with ESMTP id <0I2K00H8HV3WYL@linda-2.paradise.net.nz> for pgsql-performance@postgresql.org; Tue, 17 Aug 2004 18:23:59 +1200 (NZST) Received: from [192.168.1.11] (203-79-100-171.adsl.paradise.net.nz [203.79.100.171]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id 938559E80F; Tue, 17 Aug 2004 18:23:43 +1200 (NZST) Date: Tue, 17 Aug 2004 18:26:15 +1200 From: Mark Kirkwood Subject: Re: Strange problems with more memory. In-reply-to: <20040816182314.24818138@svb.ucs.co.za> To: Stef Cc: pgsql-performance@postgresql.org Message-id: <4121A507.1000704@coretech.co.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a2) Gecko/20040715 References: <20040816171234.5a9bac8f@svb.ucs.co.za> <14009.1092670876@sss.pgh.pa.us> <20040816182314.24818138@svb.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/252 X-Sequence-Number: 7888 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 a lot of write activity? Note that it is possible for a SELECT only workload to generate significant write activity - if the resulting datasets are too large for memory sorting or hashing. I'm *guessing* that with an 11G database and 1G (or was that 2G?) of ram that it is possible to overflow whatever your sort_mem is set to. cheers Mark Stef wrote: >Got 3 10000 rpm SCSI raid5 on here. I doubt I will get much better than that >without losing both arms and legs... > > >