Age | Commit message (Collapse) | Author |
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* 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>
|
|
* fix key_is_highlighted() and key_wants_details() so that they
don't look for flags in the label.
* fix -r -f text, g_hash-related warnings from icon cache
* add MODULE_FLAG_HIDE flag to hide module entries instead of
using the '#' at the beginning of string hack, which didn't
work everywhere, and screwed up translated strings.
* hide GPU Drawing benchmark
See: https://github.com/lpereira/hardinfo/issues/329
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
idk what.
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>
|
|
formerly required 1.0.15.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
For now 0, but planned changes.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* 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>
|
|
GTK3 build inadvertably disabled all benchmarking.
At present, the GTK3 build intentionally avoids building of "guibench"
due to non-trivial changes from GTK2 to GTK3.
However, all other benchmarks were disabled as well.
This was not by design, as non-gui benchmarks have no GTK3
dependencies.
The reason benchmarks were diasbled (did not show up in the menus)
was that the code for "benchark_gui" still referenced the missing "guibench"
routine. This routine was not present in the "benchmark.so", so the library
would not load due to the missing entry point.
This patch addresses the issue. All benchmarks (except guibench)
show/work fine with GTK3.
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
|
|
As discussed in
https://github.com/lpereira/hardinfo/issues/345
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>
|
|
(#298)
E: hardinfo no-return-in-nonvoid-function /home/abuild/rpmbuild/BUILD/hardinfo-20181022T194523/modules/benchmark/bench_results.c:137
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
The new version uses a fixed time and provides variants for
single-thread, multi-thread, and multi-core.
A few results are included.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Use just the symbolic name "hardinfo", allowing for icon packs to
provide alternative icons.
Fixes #227
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
The idea here is to make adding/removing benchmark tests easier by
having benchmark.c be the framework and all the functioned needed
for individual benchmarks live in benches.c.
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>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Other minor tweaks.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
In the future, won't have to rely on a translated string.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
For the GPU Drawing benchmark at least, it should give
some idea of the graphics capabilities of the machine.
This is the only data hardinfo currently has about that.
Maybe in the future, more advanced GPU information could
be given.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* cpu_config string is translated as loaded
* if board or cpu_desc is missing, it is left null, stored empty, and
translated to (Unknown) only when displayed.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* hide bench/name and result
* expand note for old results
The old version is kept because it is useful for future
development.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
Old versions of hardinfo used current frequency instead of max
frequency. If the cpu id string had a clock rate in it, and it is
significantly more than thre reported frequency in the benchmark
result, use that.
This feature exists in an earlier commit but it was broken.
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
* More information can be saved in benchmark.conf, while still being
compatible with older versions.
* Selecting a result give additional information about the result
and the machine the produced it.
|
|
|
|
|
|
|
|
|
|
|
|
gcc was (correctly) assuming that benchmark_parallel_for() returned
an integer, which was being to a double and messing up results. Added
the missing prototype.
Also, populate bench_results array with sane values on module init.
Some other minor cleanups in benchmark code.
|
|
|
|
|