Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 9BD4F2E00C9 for ; Thu, 27 Dec 2007 02:10:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 19197-03 for ; Thu, 27 Dec 2007 02:10:25 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id C99DB2E00C2 for ; Thu, 27 Dec 2007 02:10:35 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lBR6AT9r029360; Thu, 27 Dec 2007 01:10:29 -0500 (EST) To: Greg Smith cc: Guillaume Smet , pgsql-performance , Stefan Kaltenbrunner , =?ISO-8859-1?Q?Devrim_G=DCND=DCZ?= Subject: Re: More shared buffers causes lower performances In-reply-to: References: <1d4e0c10712251606q6f9503deye3da4b68c51bf5e@mail.gmail.com> <1198668065.4221.288.camel@ebony.site> <1d4e0c10712260741w1f141fd6x2f482143d526ad48@mail.gmail.com> <1d4e0c10712261352j2fbcd25ek1270331468d824b4@mail.gmail.com> <1d4e0c10712261453s4b171452g8aa30a1124f8fff1@mail.gmail.com> Comments: In-reply-to Greg Smith message dated "Wed, 26 Dec 2007 18:35:33 -0500" Date: Thu, 27 Dec 2007 01:10:29 -0500 Message-ID: <29359.1198735829@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/400 X-Sequence-Number: 28216 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? regards, tom lane