From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: High CPU load caused by the autovacuum launcher process |
Date: | 2018-06-08 07:28:25 |
Message-ID: | 8f4455bc-fc64-f8b3-1053-7be9085d58a8@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
On 06/08/2018 02:24 AM, Owayss Kabtoul wrote:
> Hi folks,
>
> I ran into an issue where, on Postgres instances that have a very large
> number of databases per cluster (~15K), the
I won't ask why there's a cluster with 15,000 databases...
> So auto-vacuum never really sleeps. Even changing the autovacuum_naptime
> and setting it to a much higher value (from 1min to 50min) did not have
> any effect at all. Both strace and the postgres logs showed a similar
> behaviour: lots of reads to global.stat file and constantly iterating
> through all the databases non-stop and executing autovacuum.
>
>
> Is there anything that I can do to minimize the CPU load impact that this
> process is having?
What if you disable autovacuum and run it manually?
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Deepak Goel | 2018-06-08 08:38:20 | Re: High CPU load caused by the autovacuum launcher process |
Previous Message | Owayss Kabtoul | 2018-06-08 07:24:49 | High CPU load caused by the autovacuum launcher process |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2018-06-08 08:23:02 | Re: hot_standby_feedback vs excludeVacuum and snapshots |
Previous Message | Owayss Kabtoul | 2018-06-08 07:24:49 | High CPU load caused by the autovacuum launcher process |