<feed xmlns='http://www.w3.org/2005/Atom'>
<title>hardinfo2.git/includes/benchmark.h, branch release-2.0.1pre</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.gnuabordo.com.br/debian/hardinfo2.git/atom?h=release-2.0.1pre</id>
<link rel='self' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/atom?h=release-2.0.1pre'/>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/'/>
<updated>2024-02-08T18:52:53+00:00</updated>
<entry>
<title>FIX new benchmarks working for slow &amp; fast machines</title>
<updated>2024-02-08T18:52:53+00:00</updated>
<author>
<name>bigbear</name>
<email>ns@bigbear.dk</email>
</author>
<published>2024-02-08T02:13:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/commit/?id=590da61f2e3fbcdb7493485f3e2ea359ccc0ac89'/>
<id>urn:sha1:590da61f2e3fbcdb7493485f3e2ea359ccc0ac89</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix enum declaration</title>
<updated>2020-05-09T17:47:48+00:00</updated>
<author>
<name>Trung Le</name>
<email>trung.le@ruby-journal.com</email>
</author>
<published>2020-05-07T01:27:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/commit/?id=f299962b0fa6c35e4074168abdb452cf49f6826c'/>
<id>urn:sha1:f299962b0fa6c35e4074168abdb452cf49f6826c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sysbench memory tweaks</title>
<updated>2019-10-24T14:54:09+00:00</updated>
<author>
<name>Burt P</name>
<email>pburt0@gmail.com</email>
</author>
<published>2019-09-05T03:10:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/commit/?id=c982d4e344f06a3b147d05de9476e7fcd7c9a5ac'/>
<id>urn:sha1:c982d4e344f06a3b147d05de9476e7fcd7c9a5ac</id>
<content type='text'>
* 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 &lt;pburt0@gmail.com&gt;
</content>
</entry>
<entry>
<title>benchmark: add sysbench cpu</title>
<updated>2019-08-15T03:02:42+00:00</updated>
<author>
<name>Burt P</name>
<email>pburt0@gmail.com</email>
</author>
<published>2019-08-13T15:49:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/commit/?id=bda4d418a197efab4e54990931630c9d8368d149'/>
<id>urn:sha1:bda4d418a197efab4e54990931630c9d8368d149</id>
<content type='text'>
Signed-off-by: Burt P &lt;pburt0@gmail.com&gt;
</content>
</entry>
<entry>
<title>Add wrapper for Alexey Kopytov's sysbench, memory benchmarks</title>
<updated>2019-08-15T03:02:42+00:00</updated>
<author>
<name>Burt P</name>
<email>pburt0@gmail.com</email>
</author>
<published>2019-08-13T15:12:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/commit/?id=a0b4ff82925f2c78b5fe1a9c9fe24ce0d717ce31'/>
<id>urn:sha1:a0b4ff82925f2c78b5fe1a9c9fe24ce0d717ce31</id>
<content type='text'>
Signed-off-by: Burt P &lt;pburt0@gmail.com&gt;
</content>
</entry>
<entry>
<title>Benchmark: fixes, user_note, verifiable test data</title>
<updated>2019-08-15T03:02:42+00:00</updated>
<author>
<name>Burt P</name>
<email>pburt0@gmail.com</email>
</author>
<published>2019-08-11T04:11:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/commit/?id=d17909c82b03ad0427a285c66766421751546c42'/>
<id>urn:sha1:d17909c82b03ad0427a285c66766421751546c42</id>
<content type='text'>
* 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 &lt;pburt0@gmail.com&gt;
</content>
</entry>
<entry>
<title>benchmark: add extra fields to result for revision and information</title>
<updated>2019-07-10T19:26:24+00:00</updated>
<author>
<name>Burt P</name>
<email>pburt0@gmail.com</email>
</author>
<published>2019-07-09T23:21:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/commit/?id=201513a63d65596739a05dbc051916a284194715'/>
<id>urn:sha1:201513a63d65596739a05dbc051916a284194715</id>
<content type='text'>
* 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 &lt;pburt0@gmail.com&gt;
</content>
</entry>
<entry>
<title>benchmark/blowfish: new version of blowfish benchmark</title>
<updated>2018-11-04T23:02:46+00:00</updated>
<author>
<name>Burt P</name>
<email>pburt0@gmail.com</email>
</author>
<published>2018-10-21T05:42:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/commit/?id=d5d0607e4da1bde37fc0072c65689d2ed0775ed1'/>
<id>urn:sha1:d5d0607e4da1bde37fc0072c65689d2ed0775ed1</id>
<content type='text'>
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 &lt;pburt0@gmail.com&gt;
</content>
</entry>
<entry>
<title>Fix benchmark_parallel_for() to use correct number of threads</title>
<updated>2018-02-27T15:41:51+00:00</updated>
<author>
<name>Burt P</name>
<email>pburt0@gmail.com</email>
</author>
<published>2017-12-23T14:22:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/commit/?id=6a9f6819ae661f64c3c042d48f74d6419f63580e'/>
<id>urn:sha1:6a9f6819ae661f64c3c042d48f74d6419f63580e</id>
<content type='text'>
If (end - start) / threads left a remainder, benchmark_parallel_for()
would start an extra thread for the leftover elements. Now, it has the
last thread process the few extra elements.

Added a note:
  benchmark_parallel_for(): element [start] included, but [end] is excluded.
  callback(): expected to processes elements [start] through [end] inclusive.

Signed-off-by: Burt P &lt;pburt0@gmail.com&gt;
</content>
</entry>
<entry>
<title>benchmark: New benchmark types</title>
<updated>2018-02-27T15:41:51+00:00</updated>
<author>
<name>Burt P</name>
<email>pburt0@gmail.com</email>
</author>
<published>2017-12-22T22:08:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.gnuabordo.com.br/debian/hardinfo2.git/commit/?id=01235e2d08090641b2c9c4d8344223f84f5b608d'/>
<id>urn:sha1:01235e2d08090641b2c9c4d8344223f84f5b608d</id>
<content type='text'>
New benchmark types:
* benchmark_crunch_for(): call function repeatedly for a number
  of seconds; result is number of completions.
* benchmark_parallel(): one call for each available thread
  up to n_threads; result is sum of return values.

Tweaks:
* Store return values from callback via
  benchmark_parallel_for_dispatcher()

Signed-off-by: Burt P &lt;pburt0@gmail.com&gt;
</content>
</entry>
</feed>
