Re: 8.2 is 30% better in pgbench than 8.3

From: Jim Nasby <decibel(at)decibel(dot)org>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 8.2 is 30% better in pgbench than 8.3
Date: 2007-07-23 16:49:34
Message-ID: 636BF45E-A569-457A-95A6-55DA52A76170@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 22, 2007, at 8:54 AM, Josh Berkus wrote:
> Tom,
>> Note to all: we ***HAVE TO*** settle on some reasonable default
>> vacuum_cost_delay settings before we can ship 8.3. With no cost
>> delay
>> and two or three workers active, 8.3's autovac does indeed send
>> performance into the tank.
>
> I've been using 20ms for most of my setups. That's aimed at
> reducing autovac to almost no impact at all, but taking a long
> time. Maybe 10ms?

I've found 20ms to be a pretty good number for run-of-the-mill IO
capability, and 10ms to be good for a good RAID setup (RAID10, 8+
drives, BBU).

For a default setting, I think it'd be better to lean towards 20ms.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2007-07-23 16:52:21 Re: 8.2 is 30% better in pgbench than 8.3
Previous Message Magnus Hagander 2007-07-23 16:43:44 Re: MAXIMUM_ALIGNOF on Windows-32