Horton

Re: Time to up bgwriter_lru_maxpages?

Michael Paquier <michael.paquier@gmail.com>

View thread View on postgr.es
From: Michael Paquier <michael.paquier@gmail.com>
To: Jim Nasby <Jim.Nasby@bluetreble.com>
Cc: "Joshua D. Drake" <jd@commandprompt.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2016-11-29T04:22:33Z
Lists: pgsql-hackers 
On Tue, Nov 29, 2016 at 6:20 AM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> On 11/28/16 11:53 AM, Joshua D. Drake wrote:
>>
>> On 11/28/2016 11:40 AM, Jim Nasby wrote:
>>>
>>> With current limits, the most bgwriter can do (with 8k pages) is 1000
>>> pages * 100 times/sec = 780MB/s. It's not hard to exceed that with
>>> modern hardware. Should we increase the limit on bgwriter_lru_maxpages?
>>
>>
>> Considering a single SSD can do 70% of that limit, I would say yes.
>
>
> Next question becomes... should there even be an upper limit?

Looking at the log history the current default dates of cfeca621, it
would be time to raise the bar a little bit more. Even an utterly high
value could make sense for testing.
-- 
Michael

Commits

  1. Increase upper bound for bgwriter_lru_maxpages.