File: mysql.benchmark

package info (click to toggle)
mysql-dfsg-4.1 4.1.11a-4sarge8
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 86,724 kB
  • ctags: 78,396
  • sloc: ansic: 380,120; cpp: 348,266; sh: 32,501; tcl: 30,484; perl: 20,873; yacc: 5,447; java: 4,610; makefile: 4,406; xml: 3,857; pascal: 1,795; awk: 1,338; asm: 1,064; sed: 772; sql: 503
file content (39 lines) | stat: -rw-r--r-- 1,380 bytes parent folder | download | duplicates (10)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
# This file describes how to run MySQL benchmarks with MySQL
# 

# The test was run on a Intel Xeon 2x 550 Mzh machine with 1G memory,
# 9G hard disk.  The OS is Suse 6.4, with Linux 2.2.14 compiled with SMP
# support
# Both the perl client and the database server is run
# on the same machine. No other cpu intensive process was used during
# the benchmark.

#
#
# First, install MySQL from RPM or compile it according to the
# recommendations in the MySQL manual
#

# Start MySQL

bin/safe_mysqld -O key_buffer=16M &

#
# Now we run the test that can be found in the sql-bench directory in the
# MySQL 3.23 source distribution with and without --fast
#
# Note that if you want to make a results that is comparead to some database,
# You should add "--cmp=databasename" as an extra option to the test
#
$CMP=--cmp=pg

run-all-tests --comment="Intel Xeon, 2x550 Mhz, 1G, key_buffer=16M" $CMP
run-all-tests --comment="Intel Xeon, 2x550 Mhz, 1G, key_buffer=16M" --fast $CMP

# If you want to store the results in a output/RUN-xxx file, you should
# repeate the benchmark with the extra option --log --use-old-result
# This will create a the RUN file based of the previous results
#

run-all-tests --comment="Intel Xeon, 2x550 Mhz, 1G, key_buffer=16M" --log --use-old-result $CMP
run-all-tests --comment="Intel Xeon, 2x550 Mhz, 1G, key_buffer=16M" --fast --log --use-old-result $CMP