diff options
| author | Burt P <pburt0@gmail.com> | 2019-09-04 22:10:43 -0500 |
|---|---|---|
| committer | Leandro A. F. Pereira <leandro@hardinfo.org> | 2019-10-24 07:54:09 -0700 |
| commit | c982d4e344f06a3b147d05de9476e7fcd7c9a5ac (patch) | |
| tree | 46e64f891dd306a5a7e4f18b5b7ec8022651c244 /test | |
| parent | 9b17b17c56c62bfc1b72b74e5fa623f1ad47955e (diff) | |
sysbench memory tweaks
* Use a larger sample size for sysbench 1.0+ and 64-bit
* Store pointer size with bench results
* Re-enable single thread memory benchmark
Use a larger sample size where available. The small size was
chosen because the 32-bit ARM sysbench 0.4x in raspbian
can't do more than about ~4G, but the problem is that much more
powerful machines burn through that very quickly. The result is
in MiB/s so it should still be comparable, but the results should
be more stable.
Noticed with Ryzen that multi-thread varies significantly based on
what threads are used, but benchmark doesn't really have control
over that.
Signed-off-by: Burt P <pburt0@gmail.com>
Diffstat (limited to 'test')
| -rw-r--r-- | test/just_bench.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/just_bench.sh b/test/just_bench.sh index dd1d61c8..2ae7698e 100644 --- a/test/just_bench.sh +++ b/test/just_bench.sh @@ -27,7 +27,7 @@ if [ ! -z `which sysbench` ]; then do_hi_bench "SysBench CPU (Single-thread)" do_hi_bench "SysBench CPU (Multi-thread)" #do_hi_bench "SysBench CPU (Four threads)" - #do_hi_bench "SysBench Memory (Single-thread)" + do_hi_bench "SysBench Memory (Single-thread)" #do_hi_bench "SysBench Memory (Two threads)" do_hi_bench "SysBench Memory" fi |