You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Sergei Golubchik 05aba79e98 MDEV-4447 MariaDB sources should have unix-style line endings everywhere 12 years ago
..
Comments A follow-up on WL#5154 and WL#5182: remove forgotten options. 16 years ago
Data All statements are now run in a sub transaction 25 years ago
limits MDEV-4447 MariaDB sources should have unix-style line endings everywhere 12 years ago
CMakeLists.txt Bug#16395606 SCRIPTS MISSING EXECUTE BIT 13 years ago
README README: 22 years ago
as3ap.sh Bug#11908153: CRASH AND/OR VALGRIND ERRORS IN FIELD_BLOB::GET_KEY_IMAGE 14 years ago
bench-count-distinct.sh Bug#11908153: CRASH AND/OR VALGRIND ERRORS IN FIELD_BLOB::GET_KEY_IMAGE 14 years ago
bench-init.pl.sh mysql-5.5.18 merge 14 years ago
compare-results.sh mysql-5.5.18 merge 14 years ago
copy-db.sh Bug#11908153: CRASH AND/OR VALGRIND ERRORS IN FIELD_BLOB::GET_KEY_IMAGE 14 years ago
crash-me.sh 5.3->5.5 merge 14 years ago
example Fix for BUG#36104 "INFORMATION_SCHEMA.TABLES shows TRANSACTIONAL=1 twice in CREATE_OPTIONS" 18 years ago
example.bat Import changeset 26 years ago
graph-compare-results.sh LPBUG#886526: Add propoer shebang to scripts 14 years ago
innotest1.sh MDEV-4447 MariaDB sources should have unix-style line endings everywhere 12 years ago
innotest1a.sh MDEV-4447 MariaDB sources should have unix-style line endings everywhere 12 years ago
innotest1b.sh MDEV-4447 MariaDB sources should have unix-style line endings everywhere 12 years ago
innotest2.sh MDEV-4447 MariaDB sources should have unix-style line endings everywhere 12 years ago
innotest2a.sh MDEV-4447 MariaDB sources should have unix-style line endings everywhere 12 years ago
innotest2b.sh MDEV-4447 MariaDB sources should have unix-style line endings everywhere 12 years ago
myisam.cnf Fixed problems with ma_test2 and mi_test2 on high-byte-first system 18 years ago
pwd.bat Import changeset 26 years ago
run-all-tests.sh Bug#11908153: CRASH AND/OR VALGRIND ERRORS IN FIELD_BLOB::GET_KEY_IMAGE 14 years ago
server-cfg.sh remove PBXT 12 years ago
test-ATIS.sh mysql-5.5.18 merge 14 years ago
test-alter-table.sh mysql-5.5.18 merge 14 years ago
test-big-tables.sh mysql-5.5.18 merge 14 years ago
test-connect.sh mysql-5.5.18 merge 14 years ago
test-create.sh mysql-5.5.18 merge 14 years ago
test-insert.sh Bug#11908153: CRASH AND/OR VALGRIND ERRORS IN FIELD_BLOB::GET_KEY_IMAGE 14 years ago
test-select.sh mysql-5.5.18 merge 14 years ago
test-table-elimination.sh MDEV-26: Global transaction id. Partial commit. 13 years ago
test-transactions.sh mysql-5.5.18 merge 14 years ago
test-wisconsin.sh mysql-5.5.18 merge 14 years ago
uname.bat Import changeset 26 years ago

README

The MySQL Benchmarks

These tests require a MySQL version of at least 3.20.28 or 3.21.10.

Currently the following servers are supported:
MySQL 3.20 and 3.21, PostgreSQL 6.#, mSQL 2.# and Solid Server 2.2

The benchmark directory contains the query files and raw data files used to
populate the MySQL benchmark tables. In order to run the benchmarks, you
should normally execute a command such as the following:

run-all-tests --server=mysql --cmp=mysql,pg,solid --user=test --password=test --log

This means that you want to run the benchmarks with MySQL. The
limits should be taken from all of MySQL, PostgreSQL, and Solid.
The login name and password for connecting to the server both are
``test''. The result should be saved as a RUN file in the output
directory.

When run-all-tests has finished, will have the individual results and the
the total RUN- file in the output directory.

If you want to look at some old results, use the compare-results script.
For example:

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

Some of the files in the benchmark directory are:

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
README This file.
test-ATIS.sh Creation 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 A port of the PostgreSQL version of this benchmark.
run-all-tests Use this to run all tests. When all tests are run,
use the --log and --use-old options to get a RUN-file.
compare-results Generates a comparison table from different RUN files.
server-cfg Contains the limits 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 tests 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
get things done faster.
--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 exercise 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 numbers and character strings 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.