| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Time to up bgwriter_lru_maxpages? |
| Date: | 2017-02-02 19:41:44 |
| Message-ID: | d10fcbd9-c9ff-499f-9a3c-a9208bc516e9@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/1/17 4:28 PM, Andres Freund wrote:
> On 2016-11-28 11:40:53 -0800, 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?
>
> FWIW, I think working on replacing bgwriter (e.g. by working on the
> patch I send with a POC replacement) wholesale is a better approach than
> spending time increasing limits.
Do you have a link to that? I'm not seeing anything in the archives.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-02-02 19:47:53 | Re: Time to up bgwriter_lru_maxpages? |
| Previous Message | Robert Haas | 2017-02-02 19:34:31 | Re: logical decoding of two-phase transactions |