From: Jim C. Nasby <jim@nasby.net>
To: Galy Lee <lee.galy@oss.ntt.co.jp>
To: pgsql-performance@postgresql.org, Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] how to plan for vacuum?
Date: Wed, 24 Jan 2007 21:57:42 -0600
Message-ID: <20070125035741.GE64372@nasby.net> (raw)
In-Reply-To: <20070125035202.GI26006@alvh.no-ip.org>
References: <45B6F0A8.1050705@oss.ntt.co.jp>
<20070125033917.GD64372@nasby.net>
<20070125035202.GI26006@alvh.no-ip.org>
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@nasby.net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jim@nasby.net, lee.galy@oss.ntt.co.jp, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] how to plan for vacuum?
In-Reply-To: <20070125035741.GE64372@nasby.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox