| Age | Commit message (Collapse) | Author |
|---|
|
* 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>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Until the whole bench submission framework is complete,
here is the best way to submit bench results to hardinfo.
* Run just_bench.sh to create a conf with results
* Merge those results into benchmark.conf using crudini
* Submit a pull request
Signed-off-by: Burt P <pburt0@gmail.com>
|
