Domain: benchmarkresources.com
Stories and comments across the archive that link to benchmarkresources.com.
Comments · 6
-
benchmark handbook
For those that didnt understand what TPC is and did not get enough information from http://www.tpc.org, check out further information that is very well explained at The Benchmark Handbook. The direct link is at http://www.benchmarkresources.com/handbook/conten
t s.asp.
Suhit -
benchmark handbook
For those that didnt understand what TPC is and did not get enough information from http://www.tpc.org, check out further information that is very well explained at The Benchmark Handbook. The direct link is at http://www.benchmarkresources.com/handbook/conten
t s.asp.
Suhit -
Re:There Ain't No Fair Benchmark
Just for the sake of anyone wanting a good reference for proper benchmarking, see The Benchmark Handbook (now readable online).
-
Re:My response to their response...In case anybody's interested in the benchmark that they ran, it's AS3AP, which is a pretty independant benchmark. I VERY seldom see anybody run it, but it's here:
-
Re:SurpriseThe AS3AP (which is the test where PostgreSQL was pitted against MySQL) involves transactions.
Actually, the AS3AP test that was run was the IR (information retrieval) test, just quick reads. See http://www.benchmarkresources.c om/handbook/5-3.html.
One would think that would be an environment in which MySQL would shine. But the results are actually not out of line with an earlier test run by PC Week.
Regards,
Ned Lilly
VP Hacker Relations
Great Bridge -
FactsIf you're looking for some facts, check out the original press release. Highlights:
- All tests used ODBC.
- Neither MySQL nor Interbase 6.0 were tested in TPC-C. MySQL doesn't have enough SQL92 conformance. Interbase 6.0's ODBC driver isn't ready yet. They tried to use Interbase 5.0 but couldn't get it to work.
- The test where all databases competed is the AS3AP test. A little more research shows that this is a test with mixed updates and retrievals. MySQL 3.22 is known to have poor performance with a large number of mixed updates and retrievals. This may explain why the MySQL line peaked and then fell off for this test.