aboutsummaryrefslogtreecommitdiff
path: root/modules/benchmark/zlib.c
AgeCommit message (Collapse)Author
2019-07-10benchmark: add extra fields to result for revision and informationBurt P
* add an integer revision field * add an extra information string field * zlib benchmark: new revision[1] is 2, so that old results are obviously old, and now the zlib version string will be stored in extra information. [1] as of 6a8e19a14305079b03e45eeb0580a45104f300dd Signed-off-by: Burt P <pburt0@gmail.com>
2019-06-29benchmark/zlib: new version of zlib benchmarkBurt P
The new version uses a fixed time (7s) and the results are much more consistent than the previous version. A couple results for the new version, one "low" and one "high", replace the old results, which were quite strange. Signed-off-by: Burt P <pburt0@gmail.com>
2018-12-02bench/zlib: minor fix, changes results significantlyBurt P
(#298) W: hardinfo uninitialized-variable /home/abuild/rpmbuild/BUILD/hardinfo-20181022T194523/modules/benchmark/zlib.c:28 This change significantly impacts the bench result. All old results should be discarded, IMO. I think I will also attempt to remake this benchmark in a similar way to the blowfish benchmark. See PR #293. Signed-off-by: Burt P <pburt0@gmail.com>
2018-02-27Benchmark results: store threads usedBurt P
Benchmark results store actual number of threads used by benchmark when it was run. Previously, results assumed all available threads were used. Examples: * CPU Fib only uses one * FPU FFT uses 4, 2, or 1 * N-Queens uses 10, 5, 2, or 1 Signed-off-by: Burt P <pburt0@gmail.com>
2017-07-02Add zlib benchmarkLeandro Pereira