"SfR Fresh" - the SfR Freeware/Shareware Archive 
As a special service "SfR Fresh" has tried to format the requested source page into HTML format using source code syntax highlighting with prefixed line numbers.
Alternatively you can here view or download the uninterpreted source code file.
That can be also achieved for any archive member file by clicking within an archive contents listing on the first character of the file(path) respectively on the according byte size field.
1 The MySQL Benchmarks
2
3 These tests require a MySQL version of at least 3.20.28 or 3.21.10.
4
5 Currently the following servers are supported:
6 MySQL 3.20 and 3.21, PostgreSQL 6.#, mSQL 2.# and Solid Server 2.2
7
8 The benchmark directory contains the query files and raw data files used to
9 populate the MySQL benchmark tables. In order to run the benchmarks, you
10 should normally execute a command such as the following:
11
12 run-all-tests --server=mysql --cmp=mysql,pg,solid --user=test --password=test --log
13
14 This means that you want to run the benchmarks with MySQL. The
15 limits should be taken from all of MySQL, PostgreSQL, and Solid.
16 The login name and password for connecting to the server both are
17 ``test''. The result should be saved as a RUN file in the output
18 directory.
19
20 When run-all-tests has finished, will have the individual results and the
21 the total RUN- file in the output directory.
22
23 If you want to look at some old results, use the compare-results script.
24 For example:
25
26 compare-results --dir=Results --cmp=mysql,pg,solid
27 compare-results --dir=Results --cmp=mysql,pg,solid --relative
28
29 compare-results --dir=Results --cmp=msql,mysql,pg,solid
30 compare-results --dir=Results --cmp=msql,mysql,pg,solid --relative
31
32 compare-results --dir=Results --server=mysql --same-server --cmp=mysql,pg,solid
33
34 Some of the files in the benchmark directory are:
35
36 File Description
37
38 Data/ATIS Contains data for 29 related tables used in the ATIS tests.
39 Data/Wisconsin Contains data for the Wisconsin benchmark.
40 Results Contains old benchmark results.
41 Makefile.am Automake Makefile
42 README This file.
43 test-ATIS.sh Creation of 29 tables and a lot of selects on them.
44 test-connect.sh Test how fast a connection to the server is.
45 test-create.sh Test how fast a table is created.
46 test-insert.sh Test create and fill of a table.
47 test-wisconsin.sh A port of the PostgreSQL version of this benchmark.
48 run-all-tests Use this to run all tests. When all tests are run,
49 use the --log and --use-old options to get a RUN-file.
50 compare-results Generates a comparison table from different RUN files.
51 server-cfg Contains the limits and functions for all supported
52 SQL servers. If you want to add a new server, this
53 should be the only file that neads to be changed.
54
55
56 Most of the tests should use portable SQL to make it possible to
57 compare different databases. Sometimes SQL extensions can make things
58 a lot faster. In this case the test may use the extensions if the --fast
59 option is used.
60
61 Useful options to all test-scripts (and run-all-tests):
62
63 --host=# Hostname for MySQL server (default: localhost)
64 --db=# Database to use (default: test)
65 --fast Allow use of any non-standard SQL extension to
66 get things done faster.
67 --lock-tables Use table locking to get more speed.
68
69 From a text at http://www.mgt.ncu.edu.tw/CSIM/Paper/sixth/11.html:
70
71 The Wisconsin Benchmark
72
73 The Wisconsin Benchmark described in [Bitton, DeWitt, and Turbyfill
74 1983] [Boral and DeWitt 1984] [Bitton and Turbyfill 1985] [Bitton and
75 Turbyfill 1988], and [DeWitt 1993] is the first effort to
76 systematically measure and compare the performance of relational
77 database systems with database machines. The benchmark is a
78 single-user and single-factor experiment using a synthetic database
79 and a controlled workload. It measures the query optimization
80 performance of database systems with 32 query types to exercise the
81 components of the proposed systems. The query suites include
82 selection, join, projection, aggregate, and simple update queries.
83
84 The test database consists of four generic relations. The tenk
85 relation is the key table and most used. Two data types of small
86 integer numbers and character strings are utilized. Data values are
87 uniformly distributed. The primary metric is the query elapsed
88 time. The main criticisms of the benchmark include the nature of
89 single-user workload, the simplistic database structure, and the
90 unrealistic query tests. A number of efforts have been made to extend
91 the benchmark to incorporate the multi-user test. However, they do
92 not receive the same acceptance as the original Wisconsin benchmark
93 except an extension work called the AS3AP benchmark.