Roadmap: #310 is closed, selective-scan page reads are done - #328
Merged
Conversation
Confirmed on the real 100M TSBS-cpu dataset, so the paragraph that said the issue was waiting on exactly that confirmation is no longer true. Replaced with a closing statement rather than a status line. Seven entries in this file have now gone stale, and the split is consistent: the ones that rot are statements about work in progress, and the ones that do not are statements about work that finished. Dropping restated measurements (#322) fixed the numbers; this is the other half. Refs #310, #315, #317. No issue is closed by this commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011miCFRSatixeNRw3w5yNq8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#310 closed after confirmation on the real 100M TSBS-cpu dataset. The roadmap
paragraph said it was open pending exactly that confirmation, so it went stale the
moment the issue closed.
Replaced with a closing statement: what the problem was (85 percent of the table's
pages faulted to decode one group), what it is now (3.5 percent), and the two
causes, both of them bloom filters being read when nothing would consult them.
The pattern, now with enough data points to state
Seven entries in this file have gone stale. The split is clean:
"not merged", "waiting on confirmation". Four of the seven.
#322 removed restated measurements, which fixed numbers drifting. This is the
other half of the same problem, and the fix is the same shape: prefer a sentence
that stays true. An entry describing something that finished cannot go stale; an
entry describing something in motion is perishable by construction and needs
re-checking whenever the work moves.
Docs-only.
test/docs_style.shpasses. No matrix run, no code changes.