| Age | Commit message (Collapse) | Author |
|---|
|
|
|
from copyright holders - see: https://github.com/lpereira/hardinfo/issues/530 https://github.com/lpereira/hardinfo/issues/707
|
|
|
|
* fix zlib display order
* fix cryptohash MiB/s calculation
* revision and params for other benchmarks
* allow attaching user note to bench result with -u
* don't inlcude the new result value bits if they are empty/invalid
in bench_value_to_str(). bench_value_from_str() doesn't need to be modified.
* bench_results: clean old result cpu name for x86
* use problem_marker() from dmi_memory to mark old version bench results
* benchmark: verifiable test data size and content
- The test data benchmark.data is stored in a file
that could be edited to change the size or content.
/* to guarantee size */
gchar *get_test_data(gsize min_size);
/* to checksum content */
char *md5_digest_str(const char *data, unsigned int len);
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* 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>
|
|
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>
|
|
(#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>
|
|
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>
|
|
|
