From: Denis Lussier <denisl@enterprisedb.com>
To: Leigh Dyer <leigh@eclinic.com.au>
Cc: pgsql-performance@postgresql.org
Cc: Mikael.Carneholm@wirelesscar.com
Subject: Re: Performance with 2 AMD/Opteron 2.6Ghz and 8gig
Date: Sat, 29 Jul 2006 14:09:15 -0400
Message-ID: <5f820f750607291109g6df92f86lf7d8ee7db012c3d4@mail.gmail.com> (raw)
In-Reply-To: <44CA1C81.8060703@eclinic.com.au>
References: <7F10D26ECFA1FB458B89C5B4B0D72C2B4E4D8C@sesrv12.wirelesscar.com>
<44CA1C81.8060703@eclinic.com.au>
> systems could send me their bonnie + benchmarksql results!
I am one of the authors of BenchmarkSQL, it is similar to a DBT2. But, its
very easy to use (&/or abuse). It's a multithreaded Java Swing client that
can run the exact same benchmark (uses JDBC prepared statements) against
Postgres/EnterpriseDB/Bizgres, MySQueeL, Horacle, Microsloth, etc, etc. You
can find BenchmarkSQL on pgFoundry and SourceForge.
As expected, Postgres is good on this benchmark and is getting better all
the time.
If you run an EnterpriseDB install right out of the box versus a PG install
right out of the box you'll notice that EnterpriseDB outperforms PG by
better than 2x. This does NOT mean that EnterpriseDB is 3x faster than
Postgres... EnterpriseDB is the same speed as Postgres. We do something
we call "Dynatune" at db startup time. The algorithm is pretty simple in
our current GA version and really only considers the amount of RAM, SHARED
Memory, and machine usage pattern. Manual tuning is required to really
optimize performance....
For great insight into the basics of quickly tuning PostgreSQL for a
reasonable starting point, check out the great instructions offered by Josh
Berkus and Joe Conway at http://www.powerpostgresql.com/PerfList/.
The moral of this unreasonably verbose email is that you shouldn't abuse
BenchmarkSQL and measure runs without making sure that, at least,
quick/simple best practices have been applied to tuning the db's you are
choosing to test.
--Denis Lussier
CTO
http://www.enterprisedb.com> >
>
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: denisl@enterprisedb.com, leigh@eclinic.com.au, Mikael.Carneholm@wirelesscar.com
Subject: Re: Performance with 2 AMD/Opteron 2.6Ghz and 8gig
In-Reply-To: <5f820f750607291109g6df92f86lf7d8ee7db012c3d4@mail.gmail.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