blackbeard/miner
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

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

Merged
grenade merged 1 commits from metrics/stale-semantics into main 2026-09-03 11:28:44 +00:00
Conversation 1 Commits 1 Files Changed 3
+24 -22
1 Commits
Author SHA1 Message Date
grenadeandClaude Fable 5.1 20749c622b metrics: stale work is the batch in flight at cancellation, not the whole search
ci / fmt (pull_request) Successful in 21s
Details
bench / build (pull_request) Successful in 1m1s
Details
ci / clippy (pull_request) Successful in 1m55s
Details
ci / doc (pull_request) Successful in 1m55s
Details
bench / measure (pull_request) Successful in 2m56s
Details
ci / test (pull_request) Successful in 6m35s
Details 
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