Re: High CPU load caused by the autovacuum launcher process

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Owayss Kabtoul <owayssk(at)gmail(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: High CPU load caused by the autovacuum launcher process
Date: 2018-06-08 13:59:20
Message-ID: CAMkU=1z3swfd7V+BTjDgLkxEhQ3TTf-puQMm8MVE1=ah3u9M6w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On Fri, Jun 8, 2018 at 3:24 AM, Owayss Kabtoul <owayssk(at)gmail(dot)com> wrote:

> Hi folks,
>
> I ran into an issue where, on Postgres instances that have a very large
> number of databases per cluster (~15K), the autovacuum process seems to
> have a very high impact on CPU usage. Specifically, it is the autovacuum
> launcher process, not the workers. The launcher process eats a whole CPU
> (attached is in screenshot of htop).
> ...
> 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.
>

After changing autovacuum_naptime, did you give it enough time to stabilize
at the new setting? Say, at least 3 * 50 = 150 minutes?

But overall, I would say that if you want to have 15,000 databases, you
should just resign yourself to having one CPU dedicated to this task.

Cheers,

Jeff

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2018-06-08 15:41:13 Re: High CPU load caused by the autovacuum launcher process
Previous Message Steven Crandell 2018-06-08 10:15:19 Re: High CPU load caused by the autovacuum launcher process

Browse pgsql-hackers by date

  From Date Subject
Next Message Phil Florent 2018-06-08 14:10:45 Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian
Previous Message Ashutosh Bapat 2018-06-08 13:16:44 Re: Performance regression with PostgreSQL 11 and partitioning