public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Greg Smith <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: [email protected]
Cc: Hackers <[email protected]>
Subject: Re: [HACKERS] bgwriter_lru_multiplier blurbs inconsistent
Date: Sun, 20 Jan 2008 17:05:22 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
Greg Smith <[email protected]> writes:
> There is nothing incorrect here, it's just not as clear as it could be.
> Here's a V2 that tries to clear that up:
> Unless limited by <varname>bgwriter_lru_maxpages</>, the number of dirty
> buffers written in each round is based on the number of new buffers that
> have been needed by server processes during recent rounds. The recent
> need is multiplied by <varname>bgwriter_lru_multiplier</> to arrive at the
> estimate of the number of buffers that will be needed during the next
> round. Buffers are written to meet that need if there aren't enough
> reusable ones found while scanning.
I think the main problem is the qualifying clause up front in a place
of prominence. Here's a V3 try:
The number of dirty buffers written in each round is based on the number
of new buffers that have been needed by server processes during recent
rounds. The average recent need is multiplied by
<varname>bgwriter_lru_multiplier</> to arrive at the estimate of the
number of buffers that will be needed during the next round. Dirty
buffers are written until there are that many clean, reusable buffers
available. However, no more than <varname>bgwriter_lru_maxpages</>
buffers will be written per round.
regards, tom lane
view thread (7+ messages) latest in thread
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: [HACKERS] bgwriter_lru_multiplier blurbs inconsistent
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox