Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 2BF09B5DBE1 for ; Sun, 14 Aug 2011 11:10:10 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 63148-07 for ; Sun, 14 Aug 2011 14:10:03 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.gransy.com (mail.gransy.com [82.208.29.194]) by mail.postgresql.org (Postfix) with ESMTP id 16A63B5DBBE for ; Sun, 14 Aug 2011 11:10:02 -0300 (ADT) Received: from antispam.gransy.com (antispam.gransy.com [77.78.104.124]) by mail.gransy.com (Postfix) with ESMTP id DA0914A2197 for ; Sun, 14 Aug 2011 16:10:01 +0200 (CEST) Received: from mail.gransy.com ([82.208.29.194]) by antispam.gransy.com (antispam.gransy.com [77.78.104.124]) (amavisd-new, port 10024) with ESMTP id aeyRiz0v3KS2 for ; Sun, 14 Aug 2011 16:10:01 +0200 (CEST) Received: from rc.gransy.com (elizabeth.gransy.com [89.187.132.199]) by mail.gransy.com (Postfix) with ESMTPA id C55334A2175 for ; Sun, 14 Aug 2011 16:10:01 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Sun, 14 Aug 2011 16:10:01 +0200 From: To: Subject: Re: strange pgbench results (as if blocked at the end) In-Reply-To: References: <2f9ba8ed6e4ed11d9a6d236cb4d2a2ec.squirrel@sq.gransy.com> <4E45EAD3.9030102@2ndQuadrant.com> Message-ID: <37b2e83f52518f7e9bf01bcc97b622bf@mail.gransy.com> X-Sender: tv@fuzzy.cz User-Agent: RoundCube Webmail/0.2.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201108/160 X-Sequence-Number: 44607 On Sun, 14 Aug 2011 07:15:00 -0600, Scott Marlowe wrote: > On Sun, Aug 14, 2011 at 6:51 AM, wrote: >> >> I've increased the test duration to 10 minutes, decreased the >> checkpoint timeout to 4 minutes and a checkpoint is issued just before >> the pgbench. That way the starting position should be more or less the >> same for all runs. > > Also look at increasing checkpoint completion target to something > closer to 1. 0.8 is a nice starting place. Yes, I've increased that already: checkpoints_segments=64 checkpoints_completion_target=0.9 Tomas