| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Time to up bgwriter_lru_maxpages? |
| Date: | 2017-02-02 00:28:35 |
| Message-ID: | 20170202002835.mrmpauaxkp34entx@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-02-02 01:30:30 | Re: Time to up bgwriter_lru_maxpages? |
| Previous Message | Andres Freund | 2017-02-02 00:27:40 | Re: Time to up bgwriter_lru_maxpages? |