Skip to content

csnode: backfill progress logs the average cost of a block per phase - #151

Merged
EnzinoBB merged 1 commit into
masterfrom
feat/backfill-phase-averages
Nov 1, 2026
Merged

EnzinoBB merged 1 commit into
masterfrom
feat/backfill-phase-averages

Conversation

@EnzinoBB

@EnzinoBB EnzinoBB commented Nov 1, 2026

Copy link
Copy Markdown
Collaborator

Each BACKFILL: stored down to … progress line (every 100,000 blocks) is followed by
BACKFILL: per block over the last N: verify X us, store Y us, confirmations Z us, T transactions; processor thread busy P % of the time.

Why: the slow-turn log only samples slow turns; to decide whether signature verification should move to worker threads (agreed next step after release 15) we need the average cost per phase on mainnet. Logging only; no behaviour change.

🤖 Generated with Claude Code

Each progress line (every 100,000 blocks) is followed by the average
microseconds per block spent verifying, storing and checking the round
confirmations, the transactions per block, and the share of the
processor thread the backfill took over that stretch: the measure that
decides whether the verification should move to worker threads.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@EnzinoBB
EnzinoBB merged commit b703913 into master Nov 1, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant