From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | Galy Lee <lee(dot)galy(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-performance(at)postgresql(dot)org, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] how to plan for vacuum? |
Date: | 2007-01-25 03:57:42 |
Message-ID: | 20070125035741.GE64372@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Thu, Jan 25, 2007 at 12:52:02AM -0300, Alvaro Herrera wrote:
> Jim C. Nasby wrote:
>
> > I'll generally start with a cost delay of 20ms and adjust based on IO
> > utilization.
>
> I've been considering set a default autovacuum cost delay to 10ms; does
> this sound reasonable?
For a lightly loaded system, sure. For a heavier load that might be too
much, but of course that's very dependent on not only your hardware, but
how much you want vacuum to interfere with normal operations. Though,
I'd say as a default it's probably better to be more aggressive rather
than less.
Also, it might be better to only set autovac_cost_delay by default;
presumably if someone's running vacuum by hand they want it done pronto.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-01-25 04:08:51 | pgsql: Fix for plpython functions; return true/false for boolean, |
Previous Message | Alvaro Herrera | 2007-01-25 03:52:02 | Re: how to plan for vacuum? |
From | Date | Subject | |
---|---|---|---|
Next Message | Galy Lee | 2007-01-25 10:29:20 | Re: how to plan for vacuum? |
Previous Message | Alvaro Herrera | 2007-01-25 03:52:02 | Re: how to plan for vacuum? |