From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
Cc: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 8.2 is 30% better in pgbench than 8.3 |
Date: | 2007-07-23 08:36:05 |
Message-ID: | 1185179765.4284.137.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 2007-07-22 at 08:53 -0700, Josh Berkus wrote:
> Pavel Stehule wrote:
> > Hello,
> >
> > I checked my tests again I have different results. Now I tested
> > PostgreSQL on dedicated server. Now 8.3 is about 20% faster. I didn't
> > see strong impression of autovacuum. All numbers are approximate
> > only. I did pgbench 3x for folowing configuration: (autovacuum on,
> > autovacuum off, statistics off) and for -tntransaction (100, 1000,
> > 4000)
>
> In other news, 8.3 with current HOT is 13% faster than 8.2 at TPCE in
> the first 1/2 hour. Performance does not fall over 5 hours of test run,
> and most of the main tables never have autovacuum triggered at all.
> Unfortnately, we don't yet have a 5-hour 8.2 run to compare
> last-half-hour performance.
I think the rule of thumb is if the workload doesn't have enough UPDATEs
to trigger VACUUMs then HOT will have a low benefit.
With any workload, we should run it *until* we see some autovacuums
kick-in, so we can compare the overall situation of HOT v non-HOT. HOT
is designed for longer term benefit; fillfactor benefits fade over time
(as defined).
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-07-23 08:40:27 | Re: 8.2 is 30% better in pgbench than 8.3 |
Previous Message | Magnus Hagander | 2007-07-23 07:53:07 | Re: syslogging oddity |