X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 63AB19FB3FD for ; Thu, 31 Aug 2006 14:32:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 22418-01 for ; Thu, 31 Aug 2006 14:32:18 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 5E3FD9FB2FC for ; Thu, 31 Aug 2006 14:32:18 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from shell.wgops.com (free.wgops.com [69.51.116.66]) by svr4.postgresql.org (Postfix) with ESMTP id 775D85AF8F9 for ; Thu, 31 Aug 2006 17:32:17 +0000 (GMT) Received: from [10.1.2.206] (localhost [127.0.0.1]) by shell.wgops.com (Postfix) with ESMTP id 655292570C; Thu, 31 Aug 2006 11:32:03 -0600 (MDT) Date: Thu, 31 Aug 2006 11:32:00 -0600 From: Michael Loftis To: Cosimo Streppone , Pg Performance list Subject: Re: High concurrency OLTP database performance tuning Message-ID: In-Reply-To: <44F7040E.7040805@streppone.it> References: <44F7040E.7040805@streppone.it> X-Mailer: Mulberry/4.0.4 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-MailScanner-Information: Please contact support@wgops.com X-MailScanner: WGOPS clean X-MailScanner-From: mloftis@wgops.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.739 tagged_above=0 required=5 tests=AWL, SPF_FAIL X-Spam-Level: X-Archive-Number: 200608/491 X-Sequence-Number: 20676 --On August 31, 2006 5:45:18 PM +0200 Cosimo Streppone wrote: > Good morning, > - postgresql.conf, especially: > effective_cache_size (now 5000) > bgwriter_delay (500) > commit_delay/commit_siblings (default) commit delay and siblings should be turned up, also you'll want to probably increase log_segments, unless you're not getting any warnings about it. also increase shared_buffers. i'd also make sure write caching is on on the RAID arrays as long as they're battery backed caches. > - start to use tablespaces for most intensive tables > - analyze the locks situation while queries run > - upgrade to 8.1.n > - convert db partition filesystem to ext2/xfs? > (now ext3+noatime+data=writeback) > - ??? > > Server specs: > 2 x P4 Xeon 2.8 Ghz > 4 Gb RAM > LSI Logic SCSI 2x U320 controller > 6 disks in raid 1 for os, /var, WAL > 14 disks in raid 10 for db on FC connected storage > > Current config is now (the rest is like the default): > max_connections = 100 > shared_buffers = 8192 > work_mem = 8192 > maintenance_work_mem = 262144 > max_fsm_pages = 200000 > max_fsm_relations = 1000 > bgwriter_delay = 500 > fsync = false > wal_buffers = 256 > checkpoint_segments = 32 > effective_cache_size = 5000 > random_page_cost = 2 > > Thanks for your ideas... > > -- > Cosimo > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > -- "Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler