Speed "Display Bug"

[DaViDeS0LaZz0]

Is 25842.48 Mkeys/s a Realistic Speed for Ryzen 5 5600G ? Maybe a unit or parsing error in the Cyclone display? Should I recompile it?

./Cyclone -a 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU -r 400000000000000000:7FFFFFFFFFFFFFFFFF -p 6 -j 10000000000 -s -t 16
================= WORK IN PROGRESS ==================
Target Address: 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU
Hash160 : f6f5431d25bbf7b12e8add9af5e3475c44a0a5b8
CPU Threads : 16
Mkeys/s : 22277.92
Total Checked : 3063088370186752
Elapsed Time : 38:11:34
Range : 400000000000000000:7fffffffffffffffff
Progress : 0.0003 %
Progress Save : 458
Candidates : 305796
Jumps : 305796

[DaViDeS0LaZz0]

Additional Test Evidence

After complete uninstall and recompile, the bug persists:

Test Command:

timeout 30 ./Cyclone -a 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU -r 400000000000000000:7FFFFFFFFFFFFFFFFF -p 6 -j 10000000000 -s -t 16

Mkeys/s       : 28372.10 (should be ~40.84)
Total Checked : 851179416576 (should be ~1.23e9)
Candidates    : 85 (accurate)
Jumps         : 85 (accurate)

Verification:

Small range test confirmed true speed: 40.84 Mkeys/s

Candidates counter proves actual keys checked: 85 × 16,777,216 = 1.43e9

Bug multiplier: ~695x

Conclusion: Bug is in source code, not compilation. Requires changing Total Checked counter from 32-bit to 64-bit integer type.

Ehi Dookoo2 any fix?

[Dookoo2]

This is not a bug. This is "probabilistic" search.
Deterministic search: ./Cyclone -a 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU -r 400000000000000000:7FFFFFFFFFFFFFFFFF -s -t 16
Without -p 6 -j 10000000000
Plz read read.me again.