From: Gregory Stark <stark@enterprisedb.com>
To: Euler Taveira de Oliveira <euler@timbira.com>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-advocacy@postgresql.org
Subject: Re: Sun Talks about MySQL
Date: Sat, 26 Apr 2008 02:21:21 -0400
Message-ID: <87wsmlm90e.fsf@oxford.xeocode.com> (raw)
In-Reply-To: <481278E7.9030504@timbira.com>
References: <480F8C2D.6010806@emproshunts.com>
<4811D1DD.9030401@otg-nc.com>
<20080425130105.GA19447@crankycanuck.ca>
<36e682920804250741p33d621f3gf35e6bdebe2e0531@mail.gmail.com>
<20080425152053.GE19447@crankycanuck.ca>
<Pine.GSO.4.64.0804251942060.28069@westnet.com>
<481278E7.9030504@timbira.com>
"Euler Taveira de Oliveira" <euler@timbira.com> writes:
>> I recall Heikki was doing lots of tests with DBT2 for EnterpriseDB
>> comparing those two releases like that; anybody know of a good summary I
>> could utilize there? I thought that was one of the benchmarks that got a
>> 20-30% speedup on going to 8.3 because it really took advantage of HOT in
>> particular.
If you're doing large TPC-C runs then the phantom-command-id and packed
varlena changes give you about 9% space savings which translates surprisingly
nicely into about 9% TPM increase. (This is for a specific schema, if you
dumbify your schema with char(1)s and numerics you could see a bigger
difference)
HOT has a *huge* effect on how long your can run the benchmark before
performance starts to droop. However the minimum run time for TPCC is only 2
hours and for large runs that's not enough for vacuum-related issues to kick
in.
Also, smoothed checkpoints have a *huge* effect but TPC-C is based on 95th
percentile response times and the checkpoints only affect about 1% of the
transaction response times.
I think TPC-E will make both of these major improvements much more important.
I suspect it would be hard to get 8.2 to even pass TPC-E due to the checkpoint
dropouts.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
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: stark@enterprisedb.com, euler@timbira.com, gsmith@gregsmith.com, pgsql-advocacy@postgresql.org
Subject: Re: Sun Talks about MySQL
In-Reply-To: <87wsmlm90e.fsf@oxford.xeocode.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