X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 49AC39DCC9F for ; Wed, 15 Mar 2006 15:51:11 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 18434-05 for ; Wed, 15 Mar 2006 15:51:11 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 238529DCBB2 for ; Wed, 15 Mar 2006 15:51:09 -0400 (AST) Received: from projects.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by svr4.postgresql.org (Postfix) with ESMTP id A02FF5AF96A for ; Wed, 15 Mar 2006 19:51:10 +0000 (GMT) Received: from [192.168.1.100] (or-67-76-146-141.sta.sprint-hsd.net [67.76.146.141]) (authenticated bits=0) by projects.commandprompt.com (8.13.4/8.13.4) with ESMTP id k2FJpAuf000839 for ; Wed, 15 Mar 2006 11:51:11 -0800 From: "Joshua D. Drake" Organization: Command Prompt, Inc. To: pgsql-performance@postgresql.org Subject: Re: Background writer configuration Date: Wed, 15 Mar 2006 11:54:33 -0800 User-Agent: KMail/1.9.1 References: <44181A11.EE98.0025.0@wicourts.gov> In-Reply-To: <44181A11.EE98.0025.0@wicourts.gov> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603151154.33504.jd@commandprompt.com> X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (projects.commandprompt.com [192.168.2.159]); Wed, 15 Mar 2006 11:51:11 -0800 (PST) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.088 required=5 tests=[AWL=0.088] X-Spam-Score: 0.088 X-Spam-Level: X-Archive-Number: 200603/217 X-Sequence-Number: 17654 > I then did some calculations, based on the sustained write speed of our > drive array (as measured by copying big files to it), and we tried > this: > > bgwriter_lru_percent = 20.0 > bgwriter_lru_maxpages = 200 > bgwriter_all_percent = 10.0 > bgwriter_all_maxpages = 600 > > This almost totally eliminated the clusters of timeouts, and caused the > transaction application rate to increase by a factor of eight over the > already-improved speed. (That is, we were running 30 to 35 times as > many transactions per minute into the database, compared to the default > background writer configuration.) I'm going to let these settings > settle in for a week or two before we try adjusting them further (to see > if we can eliminate those last few timeouts of this type). Can you tell us what type of array you have? Joshua D. Drake > > I guess my point is that people shouldn't be shy about boosting these > numbers by a couple orders of magnitude from the default values. It may > also be worth considering whether the defaults should be something more > aggressive. > > -Kevin > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: PLphp, PLperl - http://www.commandprompt.com/