Repository navigation
perf(telemetry): preempt long merges for generation-0 debt and cut span merge allocation - #318
Merged
Merged
Conversation
…an merge allocation An 8-vCPU benchmark of v2026.10.6-alpha still failed one gate. A higher-generation merge that started below pressure could not be interrupted, and two such merges took 132 s and 74 s. Generation-0 debt reached the hard limit meanwhile, and ingest stopped long enough for generators to time out. - When reclaimable generation-0 debt reaches the hard limit, an unprepared higher-generation merge is cancelled and generation-0 work runs immediately. Cancellation stops before PrepareReplacement and the completion marker, so recovery and publication are unchanged. - Each preemption halves the next higher-generation attempt. A minimum pair is never cancelled for debt, which guarantees higher-generation progress and bounds the wait to one pair merge. A successful higher-generation publication restores the normal ceiling. - Span merges read the three sort keys through narrow column cursors that borrow page bytes instead of rebuilding rows. Locally, a 128 x 50k span merge allocates 43% less, uses 28% less CPU, and runs 2.35 times faster idle and 1.68 times faster with six cores busy. Outputs and trace indexes are byte-identical. Locally, the forced worst-case stall was 42.8 s before and 21.9 s after, with six cores busy. Claude-Session: https://claude.ai/code/session_01XA52nWyQ3R5f5kK8kjpAQW
vishr
force-pushed
the
perf/compaction-lanes
branch
from
October 16, 2026 00:01
3ffeca0 to
5509990
Compare
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
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.
Summary
An 8-vCPU benchmark of v2026.10.6-alpha (Fanout and telemetrygen on separate ccx33s) improved on v2026.10.5:
It still failed one gate. A higher-generation merge that started below pressure could not be interrupted. Two such merges took 132 s and 74 s, generation-0 debt reached the hard limit, and ingest stopped long enough for generators to time out.
Preemption:
PrepareReplacementand the completion marker, so recovery, retired rollback sets and publication are unchanged.Span merge allocation:
Local measurements for a 128 x 50k span merge:
The forced worst-case stall went from 42.8 s to 21.9 s with six cores busy. That reproducer makes debt cross the limit during a 24M-row pair. At 300k rows/s, debt needs about 85 s to climb from 512 to 1,024 batches.
Test plan
just checkjust test-racehttps://claude.ai/code/session_01XA52nWyQ3R5f5kK8kjpAQW