Re: Final background writer cleanup for 8.3 - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Final background writer cleanup for 8.3
Date
Msg-id 46D80DA4.8010107@Yahoo.com
Whole thread Raw
In response to Re: Final background writer cleanup for 8.3  ("Heikki Linnakangas" <heikki@enterprisedb.com>)
Responses Re: Final background writer cleanup for 8.3  (Greg Smith <gsmith@gregsmith.com>)
List pgsql-hackers
On 8/24/2007 8:41 AM, Heikki Linnakangas wrote:
> If anyone out there has a repeatable test case where bgwriter does help,
> I'm all ears. The theory of moving the writes out of the critical path
> does sound reasonable, so I'm sure there is test case to demonstrate the
> effect, but it seems to be pretty darn hard to find.

One could try to dust off this TPC-W benchmark.
    http://pgfoundry.org/projects/tpc-w-php/

Again, the original theory for the bgwriter wasn't moving writes out of 
the critical path, but smoothing responsetimes that tended to go 
completely down the toilet during checkpointing, causing all the users 
to wake up and overload the system entirely.

It is well known that any kind of bgwriter configuration other than OFF 
does increase the total IO cost. But you will find that everyone who has 
SLA's that define maximum response times will happily increase the IO 
bandwidth to give an aggressively configured bgwriter room to work.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


pgsql-hackers by date:

Previous
From: Suresh_
Date:
Subject: Re: Performing antijoin in postgres
Next
From: "Merlin Moncure"
Date:
Subject: Re: enum types and binary queries