From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, 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 16:04:49 |
Message-ID: | 45B8D521.8010405@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
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/
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2007-01-25 16:06:16 | Re: tsearch in core patch, for inclusion |
Previous Message | Tom Lane | 2007-01-25 16:03:13 | Re: WAL Record Header Size Reduction |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2007-01-25 16:22:47 | Re: [PERFORM] how to plan for vacuum? |
Previous Message | Jim C. Nasby | 2007-01-25 15:54:24 | Re: how to plan for vacuum? |