X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 87F209FA4CF for ; Mon, 18 Sep 2006 19:40:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 07242-01 for ; Mon, 18 Sep 2006 22:40:32 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id EC91E9FA4D0 for ; Mon, 18 Sep 2006 19:40:31 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id ED29856437; Mon, 18 Sep 2006 17:40:30 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Mon, 18 Sep 2006 17:40:30 -0500 Date: Mon, 18 Sep 2006 17:40:30 -0500 From: "Jim C. Nasby" To: Francisco Reyes Cc: Pgsql performance Subject: Re: Vacuums on large busy databases Message-ID: <20060918224030.GM47167@enterprisedb.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060918:lists@stringsutils.com::+I/zeLcnkqKLCsFV:000000000000000 0000000000000000000000001TdV X-Hashcash: 1:20:060918:pgsql-performance@postgresql.org::bQOm09BAQRe4NyD5:00000 0000000000000000000000001eLy X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/234 X-Sequence-Number: 20920 On Thu, Sep 14, 2006 at 11:23:01AM -0400, Francisco Reyes wrote: > My setup: > Freebsd 6.1 > Postgresql 8.1.4 > Memory: 8GB > SATA Disks > > Raid 1 10 spindles (2 as hot spares) > 500GB disks (16MB buffer), 7200 rpm > Raid 10 > > Raid 2 4 spindles > 150GB 10K rpm disks > Raid 10 > > shared_buffers = 10000 > temp_buffers = 1500 > work_mem = 32768 # 32MB > maintenance_work_mem = 524288 # 512MB > > checkpoint_segments = 64 > Just increased to 64 today.. after reading this may help. Was 5 before. > > pg_xlog on second raid (which sees very little activity) BTW, on some good raid controllers (with battery backup and write-caching), putting pg_xlog on a seperate partition doesn't really help, so you might want to try combining everything. Even if you stay with 2 partitions, I'd cut pg_xlog back to just a simple mirror. -- Jim Nasby jimn@enterprisedb.com EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)