Files
xmrig-hac/src/backend/opencl
SChernykh 2af99c3d83 More precise hashrate calculation
- Use only steady timestamp counters to guarantee correctness
- CPU backend: directly measure total hashrate using raw hash counters from each thread; update data more often on ARM CPUs because they're slower
- GPU backends: directly measure total hashrate too, but use interpolator with 4 second lag to fix variance from batches of hashes

Total hashrate is now measured directly (realtime for CPU, 4 seconds lag for GPU), so it might differ a bit from the sum of all thread hashrates because data points are taken at different moments in time.

Overhead is reduced a lot since it doesn't have to go through all threads to calculate max total hashrate on every timer tick (2 times a second).
2020-10-10 11:18:01 +02:00
..
2020-10-02 17:02:52 +02:00
2020-09-25 10:53:24 +02:00
2020-08-21 08:21:51 +07:00
2019-08-27 06:31:40 +07:00
2020-03-09 01:22:34 +07:00
2020-03-09 01:22:34 +07:00
2020-05-27 16:19:57 +02:00
2020-05-27 16:19:57 +02:00
2020-03-09 01:22:34 +07:00
2020-03-09 01:22:34 +07:00
2020-10-10 11:18:01 +02:00