Files
sysbench/tests/t/test_mutex.t
Alexey Kopytov d15d273226 Fix #130: Mutex Benchmark Documentation
Fix --mutex-loops description to say it's the number of empty loops
outside the lock. Also, make the loops really empty by using a compiler
barrier instead of incrementing a local variable.
2017-04-28 17:08:54 -07:00

51 lines
1.4 KiB
Perl

########################################################################
mutex benchmark tests
########################################################################
$ args="mutex --events=10 --threads=2"
$ sysbench $args help
sysbench *.* * (glob)
mutex options:
--mutex-num=N total size of mutex array [4096]
--mutex-locks=N number of mutex locks to do per thread [50000]
--mutex-loops=N number of empty loops to do outside mutex lock [10000]
$ sysbench $args prepare
sysbench *.* * (glob)
'mutex' test does not implement the 'prepare' command.
[1]
$ sysbench $args run
sysbench *.* * (glob)
Running the test with following options:
Number of threads: 2
Initializing random number generator from current time
Initializing worker threads...
Threads started!
General statistics:
total time: *s (glob)
total number of events: 2
Latency (ms):
min: *.* (glob)
avg: *.* (glob)
max: *.* (glob)
95th percentile: *.* (glob)
sum: *.* (glob)
Threads fairness:
events (avg/stddev): */* (glob)
execution time (avg/stddev): */* (glob)
$ sysbench $args cleanup
sysbench *.* * (glob)
'mutex' test does not implement the 'cleanup' command.
[1]