From: | "Denis Lussier" <denisl(at)enterprisedb(dot)org> |
---|---|
To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
Cc: | "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org>, "Affan Salman" <affan(at)enterprisedb(dot)com>, "Peter Yarrow" <peter(dot)yarrow(at)enterprisedb(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us> |
Subject: | Re: Packed short varlenas, what next? |
Date: | 2007-03-01 06:08:46 |
Message-ID: | 64db53a00702282208o2701e17dj19327b6b69550c6f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
BenchmarkSQL is open source, but, I don't think anyone has published version
5.2 yet on pgFoundry. Amongst other goodies, version 5.2 allows for the
running of Java based tpcC and/or tpcB like benchmarks from the command line
or the cutsie gui. We've also added consistency checks to the end of the
tpc-c run (which mysql always fails).
Affan is coming out shortly with version 5.3, he'll publish by early next
week.
As a side note and different topic: The tpcB is an example of a verrryy
disk intensive little transaction. Running it with a mocked up version
COMMIT NOWAIT produces a 4x performance increase for disk setups where fsync
is not "free".
--Luss
http://www.enterprisedb.com
On 2/27/07, Gregory Stark <stark(at)enterprisedb(dot)com> wrote:
>
>
>
> I've been doing some benchmarking, I see a 9.7% space saving on the
> Benchmark-SQL 5.2 schema which translates into about a 8% performance
> gain.
> The DBT2 benchmarks show a smaller 5.3% space saving because we had
> already
> done a lot more optimizing of the schema.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-03-01 06:17:03 | Re: Resumable vacuum proposal and design overview |
Previous Message | Tom Lane | 2007-03-01 06:06:04 | Re: Is there a way to run heap_insert() AFTER ExecInsertIndexTuples() ? |