rob thijssen 20749c622b metrics: stale work is the batch in flight at cancellation, not the whole search ...

miner_stale_hashes_total was recorded in the QUIC loop for every result whose
job id no longer matched, which is every cancelled search: 74% of all hashes
on benjy flagged as stale on the first hour of data. That is the loop's
notion of a stale *result*, not wasted work; the hashes were done while the
job was current.

The wasted work is the batch that completes after the job was superseded.
Record that in the engine at the cancellation check, per device and kernel,
and drop the loop-level accounting. Expect one batch per job switch.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CBgs2nSi4H2mdh8kD8vMX5

2026-09-03 14:23:37 +03:00

..

benches

fix benches

2026-08-12 11:16:26 +08:00

examples

Different kernels for Apple Metal vs Nvidia and everything else (#92)

2026-09-01 23:21:43 +08:00

src

metrics: stale work is the batch in flight at cancellation, not the whole search

2026-09-03 14:23:37 +03:00

Cargo.toml

metrics: attribute hashrate to build, device, kernel and job outcomes

2026-09-03 14:09:43 +03:00