From: Jignesh K. Shah <J.K.Shah@Sun.COM>
To: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL publishes first real benchmark
Date: Mon, 09 Jul 2007 13:48:44 -0400
Message-ID: <469274FC.8000506@sun.com> (raw)
In-Reply-To: <469261EC.7080106@enterprisedb.com>
References: <46925AD9.9020208@sun.com>
<469261EC.7080106@enterprisedb.com>
Hi Heikki,
Heikki Linnakangas wrote:
>
> That's really exciting news!
>
> I'm sure you spent a lot of time tweaking the settings, so let me ask
> you something topical:
>
> How did you end up with the bgwriter settings you used? Did you
> experiment with different values? How much difference did it make?
>
Background writer is still a pain to get it right.. I say it is a
necessary evil since you are trying to balance it with trying to level
writes to the disks and lock contentions caused by the writer itself to
the postgresql connections. Our typical problem will arise at the high
number of users where all users are suddenly locked due to the bgwriter
holding the locks.. Using the hotuser script (which uses pearl/Dtrace
combination) we ran quite a bit of numbers trying to see which ones
results in less overall time spent in PGLock* calls and yet gave good
uniform writes to the disks. After reaching the published settings,
everynow and then we would try playing with different values to see if
it improves but generally seemed to degrade if changed.. (Of course your
mileage will vary depending on config, workload, etc).
Still I believe the locking mechanism needs to be revisited at some
point since that seems to be the one which will eventually limit the
number of users in such a workload. (Specially if you dont hit the right
settings for your workload)
Hopefully soon we will get access to bigger capacity servers and redo
SMP tests on it with the background writer.
Regards,
Jignesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: J.K.Shah@Sun.COM, heikki@enterprisedb.com
Subject: Re: PostgreSQL publishes first real benchmark
In-Reply-To: <469274FC.8000506@sun.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox