Shulou(Shulou.com)05/31 Report--

This article mainly shows you "how to use the Sysbench of the stress testing tool". The content is simple and clear. I hope it can help you solve your doubts. Let me lead you to study and learn this article "how to use the Sysbench of the stress testing tool".

1. Sysbench download

Project address: https://launchpad.net/sysbench

Download address: https://github.com/akopytov/sysbench/archive/1.0.3.tar.gz

II. Sysbench installation

[root@DB_TEST tools] # tar-xzvf sysbench-1.0.3.tar.gz

[root@DB_TEST tools] # cd sysbench-1.0.3

[root@DB_TEST sysbench-1.0.3] #. / autogen.sh

[root@DB_TEST sysbench-1.0.3] # / configure-- prefix=/usr/local/sysbench-- with-mysql

[root@DB_TEST sysbench-1.0.3] # make

[root@DB_TEST sysbench-1.0.3] # make install

[root@DB_TEST sysbench-1.0.3] # cp-rp / usr/local/sysbench/bin/sysbench / usr/bin/

[root@DB_TEST sysbench-1.0.3] # / usr/local/sysbench/bin/sysbench-- help

Click (here) to collapse or open

[root@BJ-133-22 sysbench-1.0.3] # / usr/local/sysbench/bin/sysbench-- help

Usage:

Sysbench [options]... [testname] [command]

Commands implemented by most tests: prepare run cleanup help

General options:

-- threads=N number of threads to use [1]

-- events=N limit for total number of events [0]

-- time=N limit for total execution time in seconds [10]

-- forced-shutdown=STRING number of seconds to wait after the-- time limit before forcing shutdown, or 'off' to disable [off]

-- thread-stack-size=SIZE size of stack per thread [64K]

-- rate=N average transactions rate. 0 for unlimited rate [0]

-- report-interval=N periodically report intermediate statistics with a specified interval in seconds. 0 disables intermediate reports [0]

-- report-checkpoints= [LIST,...] Dump full statistics and reset all counters at specified points in time. The argument is a list of comma-separated values representing the amount of time in seconds elapsed from start of test when report checkpoint (s) must be performed. Report checkpoints are off by default. []

-- debug [= on | off] print more debugging info [off]

-- validate [= on | off] perform validation checks where possible [off]

-- help [= on | off] print help and exit [off]

-- version [= on | off] print version and exit [off]

-- config-file=FILENAME File containing command line options

-- tx-rate=N deprecated alias for-- rate [0]

-- max-requests=N deprecated alias for-- events [0]

-- max-time=N deprecated alias for-- time [0]

-- num-threads=N deprecated alias for-- threads [1]

Pseudo-Random Numbers Generator options:

-- rand-type=STRING random numbers distribution {uniform,gaussian,special,pareto} [special]

-- rand-spec-iter=N number of iterations used for numbers generation [12]

-- rand-spec-pct=N percentage of values to be treated as' special' (for special distribution) [1]

-- rand-spec-res=N percentage of 'special' values to use (for special distribution) [75]

-- rand-seed=N seed for random number generator. When 0, the current time is used as a RNG seed. [0]

-- rand-pareto-h=N parameter h for pareto distibution [0.2]

Log options:

-- verbosity=N verbosity level {5-debug, 0-only critical messages} [3]

Percentile=N percentile to calculate in latency statistics (1-100) Use the special value of 0 to disable percentile calculations [95]

-- histogram [= on | off] print latency histogram in report [off]

General database options:

-- db-driver=STRING specifies database driver to use ('help' to get list of available drivers)

-- db-ps-mode=STRING prepared statements usage mode {auto, disable} [auto]

-- db-debug [= on | off] print database-specific debug information [off]

Compiled-in database drivers:

Mysql-MySQL driver

Mysql options:

-- mysql-host= [LIST,...] MySQL server host [localhost]

-- mysql-port= [LIST,...] MySQL server port [3306]

-- mysql-socket= [LIST,...] MySQL socket

-- mysql-user=STRING MySQL user [sbtest]

-- mysql-password=STRING MySQL password []

-- mysql-db=STRING MySQL database name [sbtest]

-- mysql-ssl [= on | off] use SSL connections, if available in the client library [off]

-- mysql-ssl-cipher=STRING use specific cipher for SSL connections []

-- mysql-compression [= on | off] use compression, if available in the client library [off]

-- mysql-debug [= on | off] trace all client library calls [off]

-- mysql-ignore-errors= [LIST,...] List of errors to ignore, or "all" [1213pr. 1020j1205]

-- mysql-dry-run [= on | off] Dry run, pretend that all MySQL client API calls are successful without executing them [off]

Compiled-in tests:

Fileio-File I do O test

Cpu-CPU performance test

Memory-Memory functions speed test

Threads-Threads subsystem performance test

Mutex-Mutex performance test

See 'sysbench help' for a list of options for each test.

III. Use of sysbench

1. CPU performance test

Cpu performance test: find the maximum prime number in the range {the shorter the time, the better.

The cpu performance test is mainly based on the addition operation of primes. Here, the maximum prime number (prime number) is specified as 80000 quotient (prime number) = `grep "processor" / proc/cpuinfo | wc-l` specifies the number of threads. The default is 1.

/ usr/local/sysbench/bin/sysbench-test=cpu-cpu-max-prime=80000 run

Click (here) to collapse or open

[root@db_test] # / usr/local/sysbench/bin/sysbench-- test=cpu-- cpu-max-prime=80000 run

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

Running the test with following options:

Number of threads: 1

Initializing random number generator from current time

Prime numbers limit: 80000

Initializing worker threads...

Threads started!

General statistics:

Total time: 10.0057s

Total number of events: 520

Latency (ms):

Min: 18.74

Avg: 19.24

Max: 19.39

95th percentile: 19.29

Sum: 10005.32

Threads fairness:

Events (avg/stddev): 520.00000.00

Execution time (avg/stddev): 10.0053 Universe 0.00

The actual CPU copying machine stress test script is as follows:

Echo-e "conduct CPU stress test: find the maximum prime number less than 10 million, the number of concurrent threads is 10, and the maximum number of requests is 100"

/ usr/local/bin/sysbench-num-threads=10-max-requests=100-test=cpu-debug-cpu-max-prime=10000000 run

2. Memory performance test

When sysbench tests memory, it reads or writes memory sequentially. Depending on the options, each thread can get global or local blocks of data during each operation.

Memory: transfer a certain amount of data throughput at different block sizes {the bigger the better}

Click (here) to collapse or open

[root@db_test fileio] # / usr/local/sysbench/bin/sysbench-- test=memory help

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

Memory options:

-- memory block size during memory-block-size=SIZE size of memory block for test [1K] testing

-- Total data size transmitted by memory-total-size=SIZE total size of data to transfer [100g]

-- memory-scope=STRING memory access scope {global,local} [global] memory access range

-- memory-hugetlb [= on | off] allocate memory from HugeTLB pool [off] allocate memory from HugeTLB pool

-- memory-oper=STRING type of memory operations {read, write, none} [write] memory operation type

Memory-access-mode=STRING memory access mode {seq,rnd} [seq] memory access method

Example: the total data transferred by the test is 5G, and each block size is 1K (generally set to 8K). In the case of continuous read and write, the throughput is 3435.87 MiB/sec.

[root@db_test fileio] # / usr/local/sysbench/bin/sysbench-test=memory-memory-block-size=1K-memory-total-size=5G run

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

Running the test with following options:

Number of threads: 1

Initializing random number generator from current time

Initializing worker threads...

Threads started!

Operations performed: 5242880 (3518332.06 ops/sec)

5120.00 MiB transferred with 3435.87 MiB/sec

General statistics:

Total time: 1.4883s

Total number of events: 5242880

Latency (ms):

Min: 0.00

Avg: 0.00

Max: 0.03

95th percentile: 0.00

Sum: 631.01

Threads fairness:

Events (avg/stddev): 5242880.0000 Universe 0.00

Execution time (avg/stddev): 0.6310Universe 0.00

Actual memory stress test script:

Echo-e "memory stress testing: test range 32G, number of concurrent threads 10, maximum number of requests 100, read"

/ usr/local/bin/sysbench-num-threads=10-max-requests=100-test=memory-memory-block-size=8K-memory-total-size=$ {MEM} G-memory-oper=read run

Echo-e "memory stress testing: test range 32G, number of concurrent threads 10, maximum number of requests 100, write"

/ usr/local/bin/sysbench-num-threads=10-max-requests=100-test=memory-memory-block-size=8K-memory-total-size=$ {MEM} G-memory-oper=write run

3. Disk IO performance test

IO performance testing: IOPS {bigger is better} in different scenarios

Click (here) to collapse or open

[root@db_test sysbench-1.0.3] # / usr/local/sysbench/bin/sysbench-- test=fileio help

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

Fileio options:

-file-num=N number of files to create [128]

-- file-block-size=N block size to use in all IO operations [16384]

-- file-total-size=SIZE total size of files to create [2G]

-- file-test-mode=STRING test mode {seqwr, seqrewr, seqrd, rndrd, rndwr, rndrw}

-- file-io-mode=STRING file operations mode {sync,async,mmap} [sync]

-file-async-backlog=N number of asynchronous operatons to queue per thread [128]

-- file-extra-flags=STRING additional flags to use on opening files {sync,dsync,direct} []

-- file-fsync-freq=N do fsync () after this number of requests (0-don't use fsync ())

-- file-fsync-all [= on | off] do fsync () after each write operation [off]

-- file-fsync-end [= on | off] do fsync () at the end of test [on]

-- file-fsync-mode=STRING which method to use for synchronization {fsync, fdatasync} [fsync]

-- file-merged-requests=N merge at most this number of IO requests if possible (0-don't merge) [0]

-- file-rw-ratio=N reads/writes ratio for combined test [1.5]

-- the number of test files created by file-num=N. Default is [128]

-- File block size during file-block-size=N testing. Default is [16384], that is, 16K.

-- the total size of file-total-size=SIZE test files. Default is [2G].

-- file-test-mode=STRING test mode {seqwr (sequential write), seqrewr (sequential read and write), seqrd (sequential read), rndrd (random read), rndwr (random write), rndrw (random read and write)}

-- file-io-mode=STRING file operation mode {sync,async,mmap} [sync]

-- file-extra-flags=STRING uses extra flags to open the file {sync,dsync,direct} []

-- file-fsync-freq=N executes fsync () frequently. 0 means not to use it. Default is 100.

-- file-fsync-all= [on | off] execute fsync () every time a write operation is performed. Default is [off].

-- file-fsync-end= [on | off] Test ends and executes fsync (). Default is [on].

-- file-fsync-mode=STRING synchronization method {fsync, fdatasync} [fsync]

-- file-merged-requests=N merges the number of IO requests if possible. Default 0 means no merging.

-- file-rw-ratio=N test read-write ratio, default [1.5]

Seqwr sequential write

Seqrewr sequential rewriting

Seqrd sequential read

Rndrd random read

Rndwr random write

Rndrw mixed random read / write

The FileIO sample 01:prepare command creates 128 files with a total size of 10G, and the file read-write mode is a random read-write mixed mode. The run command tests and returns the results, and cleanup deletes the files generated by the test!

# # Fileio preparation to generate test data (preferably 2 times the size of memory)

[root@db_test fileio] # / usr/local/sysbench/bin/sysbench-num-threads=16-test=fileio-file-total-size=10G-file-test-mode=rndrw prepare

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

WARNING:-num-threads is deprecated, use-threads instead

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

128 files, 81920Kb each, 10240Mb total

Creating files for the test...

Extra file open flags: 0

Creating file test_file.0

...

Creating file test_file.127

10737418240 bytes written in 9.96 seconds (1027.97 MiB/sec).

# # formal execution of FileIO Test

[root@db_test fileio] # / usr/local/sysbench/bin/sysbench-num-threads=16-test=fileio-file-total-size=10G-file-test-mode=rndrw run

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

WARNING:-num-threads is deprecated, use-threads instead

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

Running the test with following options:

Number of threads: 16

Initializing random number generator from current time

Extra file open flags: 0

128 files, 80MiB each

10GiB total file size

Block size 16KiB

Number of IO requests: 0

Read/Write ratio for combined random IO test: 1.50

Periodic FSYNC enabled, calling fsync () each 100requests.

Calling fsync () at the end of test, Enabled.

Using synchronous I/O mode

Doing random r/w test

Initializing worker threads...

Threads started!

File operations:

Reads/s: 1449.16

Writes/s: 965.91

Fsyncs/s: 3083.55

Throughput:

Read, MiB/s: 22.64

Written, MiB/s: 15.09

General statistics:

Total time: 10.4176s

Total number of events: 57291

Latency (ms):

Min: 0.00

Avg: 2.87

Max: 825.08

95th percentile: 0.17

Sum: 164312.66

Threads fairness:

Events (avg/stddev): 3580.6875 + 469.53

Execution time (avg/stddev): 10.2695Universe 0.08

Closely related to IO are requests per second and total throughput, of which the number of requests is (1449.16-965.91-3083.55) / s and the throughput is (22.64-15.09) MB/s

# # cleaning up created files

[root@db_test fileio] # / usr/local/sysbench/bin/sysbench-num-threads=16-test=fileio-file-total-size=10G-file-test-mode=rndrw cleanup

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

WARNING:-num-threads is deprecated, use-threads instead

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

Removing test files...

Real-world FILEIO stress test script:

Echo-e "IO stress test: 20 files, each 10GB, random read and write"

/ usr/local/bin/sysbench-file-num=20-num-threads=20-test=fileio-file-total-size=$ {HDD} G-max-requests=1000000-file-test-mode=rndrw prepare

/ usr/local/bin/sysbench-file-num=20-num-threads=20-test=fileio-file-total-size=$ {HDD} G-max-requests=1000000-file-test-mode=rndrw run

/ usr/local/bin/sysbench-file-num=20-num-threads=20-test=fileio-file-total-size=$ {HDD} G-max-requests=1000000-file-test-mode=rndrw cleanup

4. Thread test

Thread scheduling: thread execution concurrently, cycle response semaphore time spent {less, better}

Test the performance of the thread scheduler. Testing the behavior of the thread scheduler under high load is very useful for testing the performance of the thread scheduler. Useful for testing the behavior of the thread scheduler under high load

Click (here) to collapse or open

[root@db_test fileio] # / usr/local/sysbench/bin/sysbench-- test=threads help

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

Threads options:

-- thread-yields=N number of yields to do per request [1000] how many threads are generated per request. Default is [1000].

-- thread-locks=N number of locks per thread [8] number of locks per thread. Default is [8]

Example:

[root@db_test fileio] # / usr/local/sysbench/bin/sysbench-num-threads=64-test=threads-thread-yields=100-thread-locks=2 run

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

WARNING:-num-threads is deprecated, use-threads instead

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

Running the test with following options:

Number of threads: 64

Initializing random number generator from current time

Initializing worker threads...

Threads started!

General statistics:

Total time: 10.0043s

Total number of events: 102842

Latency (ms):

Min: 0.02

Avg: 6.22

Max: 28.83

95th percentile: 15.00

Sum: 640039.96

Threads fairness:

Events (avg/stddev): 1606.9062 Universe 31.79

Execution time (avg/stddev): 10.0006 Universe 0.00

5. Mutex test

Mutex: the time it takes for a concurrent thread to apply for a mutex loop a certain number of times at the same time {as little as possible}

Test the performance of the mutex by simulating all threads running concurrently at the same time and requesting the mutex briefly

Click (here) to collapse or open

[root@db_test fileio] # / usr/local/sysbench/bin/sysbench-- test=mutex help

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

Mutex options:

-- mutex-num=N total size of mutex array [4096] array mutex total size. Default is [4096].

-- mutex-locks=N number of mutex locks to do per thread [50000] number of mutexes per thread. Default is [50000].

-- number of empty cycles in mutex-loops=N number of empty loops to do inside mutex lock [10000] internal mutexes. Default is [10000].

All threads execute at the same time to get a short amount of mutex lock to test the implementation of mutex!

Example:

[root@db_test fileio] # / usr/local/sysbench/bin/sysbench-test=mutex-mutex-num=4096-mutex-locks=50000-mutex-loops=20000 run

WARNING: the-- test option is deprecated. You can pass a script name or path on the command line without any options.

Sysbench 1.0.3 (using bundled LuaJIT 2.1.0-beta2)

Running the test with following options:

Number of threads: 1

Initializing random number generator from current time

Initializing worker threads...

Threads started!

General statistics:

Total time: 0.0021s

Total number of events: 1

Latency (ms):

Min: 2.05

Avg: 2.05

Max: 2.05

95th percentile: 2.03

Sum: 2.05

Threads fairness:

Events (avg/stddev): 1.0000amp 0.00

Execution time (avg/stddev): 0.0020amp 0.00

The above is all the contents of the article "how to use the Sysbench of stress testing tools". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.