From: Joshua D. Drake <jd@commandprompt.com>
To: 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: Thu, 25 Jan 2007 08:04:49 -0800
Message-ID: <45B8D521.8010405@commandprompt.com> (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>
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?
It really depends on the system. Most of our systems run anywhere from
10-25ms. I find that any more than that, Vacuum takes too long.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
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: jd@commandprompt.com, jim@nasby.net, lee.galy@oss.ntt.co.jp, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] how to plan for vacuum?
In-Reply-To: <45B8D521.8010405@commandprompt.com>
* 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