Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 3A0BA1337BA0 for ; Mon, 7 Mar 2011 10:22:30 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 91049-08-3 for ; Mon, 7 Mar 2011 14:22:22 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mh5.mail.rice.edu (mh5.mail.rice.edu [128.42.199.32]) by mail.postgresql.org (Postfix) with ESMTP id 7DBC41337BD0 for ; Mon, 7 Mar 2011 10:22:17 -0400 (AST) Received: from mh5.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh5.mail.rice.edu (Postfix) with ESMTP id C702F28F89A; Mon, 7 Mar 2011 08:22:17 -0600 (CST) X-Virus-Scanned: by amavis-2.6.4 at mh5.mail.rice.edu, auth channel Received: from mh5.mail.rice.edu ([127.0.0.1]) by mh5.mail.rice.edu (mh5.mail.rice.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id UxM3FHACfTeb; Mon, 7 Mar 2011 08:22:17 -0600 (CST) X-SMTP-Auth: no X-SMTP-Auth: no Received: from aart.is.rice.edu (aart.is.rice.edu [168.7.56.48]) by mh5.mail.rice.edu (Postfix) with ESMTP id 9900B28F86B; Mon, 7 Mar 2011 08:22:17 -0600 (CST) Received: by aart.is.rice.edu (Postfix, from userid 18612) id 4213F2D5A6; Mon, 7 Mar 2011 08:22:16 -0600 (CST) Date: Mon, 7 Mar 2011 08:22:16 -0600 From: Kenneth Marshall To: Andreas For? Tollefsen Cc: pgsql-performance@postgresql.org Subject: Re: Performance issues Message-ID: <20110307142216.GM8169@aart.is.rice.edu> References: <20110307140101.GL8169@aart.is.rice.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.21 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201103/68 X-Sequence-Number: 42747 On Mon, Mar 07, 2011 at 03:17:05PM +0100, Andreas For? Tollefsen wrote: > Thanks, Ken. > > It seems like the tip to turn off synchronous_commit did the trick: > > /usr/lib/postgresql/8.4/bin/pgbench -T 60 test1 > starting vacuum...end. > transaction type: TPC-B (sort of) > scaling factor: 1 > query mode: simple > number of clients: 1 > duration: 60 s > number of transactions actually processed: 86048 > tps = 1434.123199 (including connections establishing) > tps = 1434.183362 (excluding connections establishing) > > Is this acceptable compared to others when considering my setup? > > Cheers, > Andreas > These are typical results for synchronous_commit off. The caveat is you must be able to handle loosing transactions if you have a database crash, but your database is still intact. This differs from turning fsync off in which a crash means you would need to restore from a backup. Cheers, Ken