Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from copyright holders - see: https://github.com/lpereira/hardinfo/issues/530 https://github.com/lpereira/hardinfo/issues/707
|
|
|
|
|
|
|
|
|
|
Related to #599.
|
|
Now that the sync manager is working fine, and we have the same
data in a structured way in JSON files, reading from this legacy
format doesn't need to be supported any longer.
|
|
|
|
Fixes #552.
|
|
Recent cleanups broke this function and the server was rejecting MachineIds.
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
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>
|
|
Signed-off-by: Burt P <pburt0@gmail.com>
|
|
For now 0, but planned changes.
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>
|
|
As discussed in
https://github.com/lpereira/hardinfo/issues/345
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>
|
|
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>
|
|
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.
|