From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | daveg(at)sonic(dot)net |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #13750: Autovacuum slows down with large numbers of tables. More workers makes it slower. |
Date: | 2015-10-30 13:46:46 |
Message-ID: | 20151030134646.GE5726@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg토토 꽁 머니SQL : Postg토토 꽁 머니SQL 메일 링리스트 : 2015-10-30 이후 PGSQL-BUGS 13:46 |
daveg(at)sonic(dot)net wrote:
> With more than a few tens of thousands of tables in one database
> autovacuuming slows down radically and becomes ineffective. Increasing the
> number of autovacuum workers makes the slow down worse.
Yeah, you need to decrease autovacuum_vacuum_cost_delay if you want to
make them go faster. (As more workers are started, the existing ones
slow down. The intent is that the I/O bandwidth allocation is kept
constant regardless of how many workers there are.)
> When they updated to 9.4.4 they also increased the number of autovacuum
> workers in anticipation of the multixact fix causing extra vacuuming.
> Several days later they observed massive catalog bloat, eg pg_attribute was
> over 200GB of mostly empty pages. This caused new connections to get stuck
> in startup as the catalogs no longer fit in the buffer cache.
Oh crap.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David Gould | 2015-10-30 14:27:04 | Re: BUG #13750: Autovacuum slows down with large numbers of tables. More workers makes it slower. |
Previous Message | daveg | 2015-10-30 13:32:52 | BUG #13750: Autovacuum slows down with large numbers of tables. More workers makes it slower. |