Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 0A0292E02CF for ; Thu, 27 Dec 2007 04:48:04 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 28309-10 for ; Thu, 27 Dec 2007 04:48:01 -0400 (AST) Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 1B7602E0263 for ; Thu, 27 Dec 2007 04:48:01 -0400 (AST) Received: by svr2.hagander.net (Postfix, from userid 1000) id 03F94DCCDD7; Thu, 27 Dec 2007 09:47:59 +0100 (CET) Date: Thu, 27 Dec 2007 09:47:59 +0100 From: Magnus Hagander To: Tom Lane Cc: Greg Smith , Guillaume Smet , pgsql-performance , Stefan Kaltenbrunner , Devrim =?iso-8859-1?B?R9xORNxa?= Subject: Re: More shared buffers causes lower performances Message-ID: <20071227084759.GB23218@svr2.hagander.net> References: <1d4e0c10712251606q6f9503deye3da4b68c51bf5e@mail.gmail.com> <1198668065.4221.288.camel@ebony.site> <1d4e0c10712260741w1f141fd6x2f482143d526ad48@mail.gmail.com> <1d4e0c10712261352j2fbcd25ek1270331468d824b4@mail.gmail.com> <1d4e0c10712261453s4b171452g8aa30a1124f8fff1@mail.gmail.com> <29359.1198735829@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29359.1198735829@sss.pgh.pa.us> User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/404 X-Sequence-Number: 28220 On Thu, Dec 27, 2007 at 01:10:29AM -0500, Tom Lane wrote: > Greg Smith writes: > > On Wed, 26 Dec 2007, Guillaume Smet wrote: > >> beta RPMs are by default compiled with --enable-debug and > >> --enable-cassert which doesn't help them to fly fast... > > > Got that right. Last time I was going crazy after running pgbench with > > those options and not having realized what I changed, I was getting a 50% > > slowdown on results that way compared to without the debugging stuff. > > Didn't realize it scaled with shared_buffers though. > > See AtEOXact_Buffers(). There are probably any number of other > interesting scaling behaviors --- in my tests, AllocSetCheck() is > normally a major cycle-eater if --enable-cassert is set, and that costs > time proportional to the number of memory chunks allocated by the query. > > Currently the docs say that --enable-cassert > > Enables assertion checks in the server, which test for > many cannot happen conditions. This is invaluable for > code development purposes, but the tests slow things down a little. > > Maybe we ought to put that more strongly --- s/a little/significantly/, > perhaps? Sounds like a good idea. We got bit by the same thing when doing some benchmarks on the MSVC port (and with we I mean Dave did the work, and several people couldn't understand why the numbers sucked) //Magnus