Skip to content

confirm: walk past taken BQ hole; loadq=14 writeq=14 - #137

Merged
reardencode merged 2 commits into
masterfrom
confirm/lookup-taken-walk
Aug 18, 2026
Merged

confirm: walk past taken BQ hole; loadq=14 writeq=14#137
reardencode merged 2 commits into
masterfrom
confirm/lookup-taken-walk

Conversation

@rearden-grok

@rearden-grok rearden-grok Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Why

After loadq, lookup take_raws the BQ row when it emits a batch. The next block_queue_unresolved_heights(path_lo=tip+1) saw a hole at tip+1 and returned empty, so lookup idled after one wave (~18–25 fat blocks). Scripts sat at scriptq=1 while 200+ later heights sat on the BQ. Host rate at 932–943k dropped ~6.2/s → ~4.4/s.

What

  • Query walk starts at max(path_lo, lookup_taken_hi+1). A missing height above that high-water is still a fetch hole.
  • Pin: unresolved_heights_walks_past_taken_bq_hole (store walker unchanged).
  • Queue caps: loadq=14 · scriptq=4 · writeq=14 (the knobs already on the host).

Test

cargo test -p rbitcoin-query --lib unresolved_heights
cargo test -p rbitcoin-store --lib unresolved_heights_
cargo test -p rbitcoin-net --lib queue_depth_log_and_caps_surface

rearden-grok Bot added 2 commits August 18, 2026 13:17
take_raw removes the BQ row, so unresolved_heights starting at
tip+1 treated the taken prefix as a fetch hole and lookup idled
after one wave. Start the walk after lookup_taken_hi; a missing
height above that high-water still stops.

Queue caps match the running host knobs (14/4/14).
format_info / format_debug / format_sizes pin the live default cap.
@reardencode
reardencode merged commit 930bcf0 into master Aug 18, 2026
13 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