Coming soon: SQL based searching of the database! Stay tuned.
Download your copy of the benchmarking script here: http://code.google.com/p/dbbenchmark/
Coming soon: SQL based searching of the database! Stay tuned.
Download your copy of the benchmarking script here: http://code.google.com/p/dbbenchmark/
Arclite theme by digitalnature | powered by WordPress
Pingback: Site launched « db benchmark.com
Pingback: dbbenchmark.com – MySQL benchmarking now supports multiple threads! « db benchmark.com
#1 by Alejandro on 2010/08/30 - 10:33 PM
Quote
I’m the one who submitted the Q9550 2.83GHz result. Sorry for doing it 2 times, please, delete one.
BTW: I can’t believe our DB is the fastest, The CPU was even running at 2.0 GHz!!!
#2 by Daniël van Eeden on 2010/08/31 - 7:55 AM
Quote
I’ve submitted the 5.1.50-enterprise-gpl-advanced.
#3 by admin on 2010/08/31 - 9:29 PM
Quote
Multiple submissions are fine – feel free to run/submit more than once.
#4 by John on 2010/09/02 - 1:47 PM
Quote
nice, i’m 2010-09-02 06:36:22. running a vm on top of win7
#5 by sammy on 2010/09/02 - 9:35 PM
Quote
Sorry, i dont understand the values. It is good to have less INSERT_TX_Y per second or do I favour a lot of INSERT_TX_Y per second? How to read the benchmark results?
#6 by admin on 2010/09/02 - 9:45 PM
Quote
I assume you’re asking if you should favor INSERT_TX_Y or INSERT_TX_N values? This depends on what engine you’re testing. Transaction support (INSERT_TX_Y) is for testing InnoDB or other transactional engines. INSERT_TX_N is for testing non-transactional engines like MyISAM. As to the values of any stat, higher is better. More operations per second means better performance.