| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | rihad <rihad(at)mail(dot)ru> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: When do vacuumed pages/tuples become available for reuse? |
| Date: | 2019-04-11 15:54:30 |
| Message-ID: | CAMkU=1w5tuRcA_BuNgs+cd-VgpZ71RBw=RyOykvDo0+JeDCyfQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 11, 2019 at 11:14 AM rihad <rihad(at)mail(dot)ru> wrote:
> autovacuum_vacuum_scale_factor = 0.01
> autovacuum_vacuum_threshold = 50
This seems counterproductive. You need to make the vacuum more efficient,
not more frantic.
> autovacuum_vacuum_cost_delay = 10ms
> autovacuum_vacuum_cost_limit = 400
>
> Anything more than that and we risk impacting the performance of user
> queries.
>
Well, unbounded bloat will also impact the user queries--eventually. Was
this an experimental determination? Can you tell what about the autovac
most impacts the user queries, the reading or the writing?
You might just have more workload than your hardware can handle. There is
always going to be some fundamental limit, and while you can tune your way
up to that limit, you can't tune your way past it.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2019-04-11 16:09:34 | Re: When do vacuumed pages/tuples become available for reuse? |
| Previous Message | rihad | 2019-04-11 15:44:04 | Re: When do vacuumed pages/tuples become available for reuse? |