| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autovacuum can't keep up, bloat just continues to rise |
| Date: | 2017-07-19 23:16:30 |
| Message-ID: | c466ccb1-de05-bc63-f618-55b7f50d8e0e@joeconway.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/19/2017 03:29 PM, Tom Lane wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>> At PGConf US Philly last week I was talking with Jim and Jan about
>> performance. One of the items that came up is that PostgreSQL can't run
>> full throttle for long periods of time. The long and short is that no
>> matter what, autovacuum can't keep up. This is what I have done:
>
> Try reducing autovacuum_vacuum_cost_delay more, and/or increasing
> autovacuum_vacuum_cost_limit.
I would try
autovacuum_vacuum_cost_delay = 0
and for any tables > 1 million rows:
autovacuum_vacuum_scale_factor: 0
autovacuum_vacuum_threshold: 100000 (perhaps even smaller)
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2017-07-19 23:17:35 | Re: JSONB - JSONB operator feature request |
| Previous Message | Alvaro Herrera | 2017-07-19 22:54:01 | Re: autovacuum can't keep up, bloat just continues to rise |