From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Jesper Krogh <jesper(at)krogh(dot)cc>, pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Aggressive autovacuuming ? |
Date: | 2010-06-21 16:36:54 |
Message-ID: | 1277137973-sup-953@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Excerpts from Scott Marlowe's message of dom jun 20 16:13:15 -0400 2010:
> On Sun, Jun 20, 2010 at 11:44 AM, Jesper Krogh <jesper(at)krogh(dot)cc> wrote:
> > Hi.
> >
> > I have been wondering if anyone has been experimenting with "really
> > agressive"
> > autovacuuming.
>
> I have been using moderately aggressive autovac, with 6 or more
> threads running with 1ms sleep, then keeping track of them to see if
> they're being too aggresive. Basically as long as io utilization
> doesn't hit 100% it doesn't seem to have any negative or even
> noticeable effect.
Keep in mind that autovacuum scales down the cost limit the more workers
there are. So if you have 10ms sleeps and 1 worker, it should roughly
use a similar amount of I/O than if you have 10ms sleeps and 10 workers
(each worker would sleep 10 times more frequently).
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-06-21 17:01:38 | Re: Aggressive autovacuuming ? |
Previous Message | Sergio Charpinel Jr. | 2010-06-21 14:42:14 | Low perfomance SUM and Group by large databse |