Go to the first, previous, next, last section, table of contents.
This should contain a technical description of the MySQL
benchmark suite (and crash-me) but that description is not
written yet. Currently, you should look at the code and results in the
`sql-bench' directory in the distribution (and of course on the web
page at http://www.mysql.com/crash-me-choose.htmy and (normally found in the `sql-bench' directory in the MySQL
distribution)).
It is meant to be a benchmark that will tell any user what things a
given SQL implementation performs well or poorly at.
Note that this benchmark is single threaded so it measures the minimum
time for the operations.
For example (run on the same NT 4.0 machine):
Reading 2000000 rows by index | Seconds | Seconds
| | mysql | 367 | 249
|
| mysql_odbc | 464
|
| db2_odbc | 1206
|
| informix_odbc | 121126
|
| ms-sql_odbc | 1634
|
| oracle_odbc | 20800
|
| solid_odbc | 877
|
| sybase_odbc | 17614
|
Inserting (350768) rows | Seconds | Seconds
| | mysql | 381 | 206
|
| mysql_odbc | 619
|
| db2_odbc | 3460
|
| informix_odbc | 2692
|
| ms-sql_odbc | 4012
|
| oracle_odbc | 11291
|
| solid_odbc | 1801
|
| sybase_odbc | 4802
|
In the above test MySQL was run with a 8M index cache.
Note that Oracle is not included since they asked to be removed. All
Oracle benchmarks has to be passed by Oracle! We believe that makes
Oracle benchmarks VERY biased since the above bechmarks are
supposed to show that a standard installation can do for a single
client.
crash-me tries to determine what features a database supports and
what its capabilities and limitations are by actually running
queries. For example, it determines:
-
What column types are supported
-
How many indexes are supported
-
What functions are supported
-
How big a query can be
-
How big a
VARCHAR column can be
Go to the first, previous, next, last section, table of contents.
| 
