On Thu, Jan 25, 2007 at 08:04:49AM -0800, Joshua D. Drake wrote:
>
> 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.
How do you measure the impact of setting it to 12 as opposed to 15?
-
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 any
Please cc the list so others can reply as well...
On Thu, Jan 25, 2007 at 08:45:50AM +0100, Tomas Vondra wrote:
> > On Wed, Jan 24, 2007 at 02:37:44PM +0900, Galy Lee wrote:
> >> 1. How do we know if autovacuum is enough for my application, or should
> >> I setup a vacuum manually from cron f
On Thu, Jan 25, 2007 at 07:29:20PM +0900, Galy Lee wrote:
> so what is the principle to set them?
> - keep dead space lower than some disk limit
> - or keep the garbage rate lower than fillfactor
> or any other general principle?
How do you measure "dead space" and "garbage rate?"
I'm a newbe
Jim C. Nasby wrote:
On Wed, Jan 24, 2007 at 02:37:44PM +0900, Galy Lee wrote:
1. How do we know if autovacuum is enough for my application, or should
I setup a vacuum manually from cron for my application?
Generally I trust autovac unless there's some tables where it's critical
that the
