From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
Cc: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Devrim GÜNDÜZ <devrim(at)commandprompt(dot)com> |
Subject: | Re: More shared buffers causes lower performances |
Date: | 2007-12-27 06:10:29 |
Message-ID: | 29359.1198735829@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Greg Smith <gsmith(at)gregsmith(dot)com> 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 <firstterm>assertion</> checks in the server, which test for
many <quote>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
From | Date | Subject | |
---|---|---|---|
Next Message | Shane Ambler | 2007-12-27 07:16:38 | Re: With 4 disks should I go for RAID 5 or RAID 10 |
Previous Message | Mark Mielke | 2007-12-27 04:36:27 | Re: With 4 disks should I go for RAID 5 or RAID 10 |