mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 12:02:42 +01:00
765940cb3a
Fixed that @VAR shows all decimals Fixed problem with FLUSH TABLES and LOCK TABLE CREATE ... SELECT now creates keys later Reset AUTO_INCREMENT order if droping AUTO_INCREMENT key Docs/manual.texi: Added MySQL/PostgreSQL comparison isam/_dynrec.c: Fixed wrong compare (not used in MySQL) myisam/mi_dynrec.c: Fixed wrong compare (not used in MySQL). Changed compare to use my_pread() myisam/mi_packrec.c: cleanup mysql-test/r/alter_table.result: Added test for ALTER TABLE mysql-test/r/variables.result: Added test for variables with REAL values. mysql-test/t/alter_table.test: Added test for ALTER TABLE mysql-test/t/variables.test: Added test for variables with REAL values. mysys/my_pread.c: Cleanup sql-bench/Makefile.am: removed extra \ sql-bench/README: Fixed typo. sql/item_func.cc: Fixed that @VAR shows all decimals sql/share/swedish/errmsg.OLD: update sql/sql_base.cc: Fixed problem with FLUSH TABLES and LOCK TABLE sql/sql_insert.cc: CREATE ... SELECT now creates keys later sql/sql_table.cc: Reset AUTO_INCREMENT order if droping AUTO_INCREMENT key. BitKeeper/etc/ignore: Added sql-bench/graph-compare-results to the ignore list BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
97 lines
4.2 KiB
Text
Executable file
97 lines
4.2 KiB
Text
Executable file
The MySQL Benchmarks
|
|
|
|
These tests needs a MySQL version of at least 3.20.28 or 3.21.10.
|
|
NOTE: With MySQL 3.20.# you have to use '--skip-in', because MySQL 3.20
|
|
doesn't support the IN operator.
|
|
|
|
Currently the following servers are supported:
|
|
MySQL 3.20 and 3.21, PostgreSQL 6.#, mSQL 2.# and Solid Server 2.2
|
|
|
|
In this directory are the queries and raw data files used to populate
|
|
the MySQL benchmarks. In order to run the benchmarks you should normally
|
|
execute a command like the following:
|
|
|
|
run-all-tests --server=mysql --cmp=mysql,pg,solid --user=test --password=test --log
|
|
|
|
The above means that one wants to run the benchmark with MySQL. The limits
|
|
should be taken from all of mysql,PostgreSQL and Solid. Login name and
|
|
password is 'test'. The result should be saved as a RUN file in the output
|
|
directory.
|
|
|
|
When the above script has run you will have the individual results and the
|
|
the total RUN- file in the output directory.
|
|
|
|
If you want to look at some old results, try:
|
|
|
|
compare-results --dir=Results --cmp=mysql,pg,solid
|
|
compare-results --dir=Results --cmp=mysql,pg,solid --relative
|
|
|
|
compare-results --dir=Results --cmp=msql,mysql,pg,solid
|
|
compare-results --dir=Results --cmp=msql,mysql,pg,solid --relative
|
|
|
|
compare-results --dir=results --server=mysql --same-server --cmp=mysql,pg,solid
|
|
|
|
|
|
File Description
|
|
|
|
Data/ATIS Contains data for 29 related tables used in the ATIS tests.
|
|
Data/Wisconsin Contains data for the Wisconsin benchmark.
|
|
Results Contains old benchmark results.
|
|
Makefile.am Automake Makefile
|
|
Overview-paper A paper nicked from the net about database bench-
|
|
marking.
|
|
README This file.
|
|
test-ATIS.sh Cretation of 29 tables and a lot of selects on them.
|
|
test-connect.sh Test how fast a connection to the server is.
|
|
test-create.sh Test how fast a table is created.
|
|
test-insert.sh Test create and fill of a table.
|
|
test-wisconsin.sh This is a port of the PostgreSQL version of this
|
|
benchmark.
|
|
run-all-test Use this to run all tests. When all test are run,
|
|
use the --log --use-old option to get a RUN-file.
|
|
compare-results Makes a compare table from different RUN files.
|
|
server-cfg Contains the limit and functions for all supported
|
|
SQL servers. If you want to add a new server, this
|
|
should be the only file that neads to be changed.
|
|
|
|
|
|
Most of the test should use portable SQL to make it possible to
|
|
compare different databases. Sometimes SQL extensions can make things
|
|
a lot faster. In this case the test may use the extensions if the --fast
|
|
option is used.
|
|
|
|
Useful options to all test-scripts (and run-all-tests):
|
|
|
|
--host=# Hostname for MySQL server (default: localhost)
|
|
--db=# Database to use (default: test)
|
|
--fast Allow use of any non-standard SQL extension to
|
|
do the get things done faster.
|
|
--skip-in Don't do test with the IN operation (if the SQL server
|
|
hasn't implemented this, for example mSQL and MySQL 3.20).
|
|
--lock-tables Use table locking to get more speed.
|
|
|
|
From a text at http://www.mgt.ncu.edu.tw/CSIM/Paper/sixth/11.html
|
|
|
|
The Wisconsin Benchmark
|
|
|
|
The Wisconsin Benchmark described in [Bitton, DeWitt, and Turbyfill
|
|
1983] [Boral and DeWitt 1984] [Bitton and Turbyfill 1985] [Bitton and
|
|
Turbyfill 1988], and [DeWitt 1993] is the first effort to
|
|
systematically measure and compare the performance of relational
|
|
database systems with database machines. The benchmark is a
|
|
single-user and single-factor experiment using a synthetic database
|
|
and a controlled workload. It measures the query optimization
|
|
performance of database systems with 32 query types to exe cise the
|
|
components of the proposed systems. The query suites include
|
|
selection, join, projection, aggregate, and simple update queries.
|
|
|
|
The test database consists of four generic relations. The tenk
|
|
relation is the key table and most used. Two data types of small
|
|
integer number and character string are utilized. Data values are
|
|
uniformly distributed. The primary metric is the query elapsed
|
|
time. The main criticisms of the benchmark include the nature of
|
|
single-user workload, the simplistic database structure, and the
|
|
unrealistic query tests. A number of efforts have been made to extend
|
|
the benchmark to incorporate the multi-user test. However, they do
|
|
not receive the same acceptance as the original Wisconsin benchmark
|
|
except an extension work called the AS3AP benchmark.
|