docs: in-place index builds measured with the shipped operator - #84
Merged
Merged
Conversation
The premise compared the copy path with the engines' own non-blocking statements. This runs LocalCutover.index from f77bb7b against the copy path on the same tables, with a process on the map in force writing throughout. At 450 000 rows on PostgreSQL the copy path's cutover ran into the operator's 30 s watchdog and a recovery aborted it, leaving the decided index out of force; the in-place build was published in 618 ms. On ClickHouse the same table still fitted, 2.2 s inside the budget. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
What
The post-implementation measurement for in-place index builds (#83): the shipped operator -
LocalCutover.indexfromf77bb7b- against the copy path on the same tables, with a process on the map in force writing a row every 5 ms throughout. Script, raw results, load readings and SHA-256 sums indocs/qualification/in-place-index/after/.At 450 000 rows on PostgreSQL the copy path cannot carry out the model's decision at all; the in-place build publishes it in 618 ms. On ClickHouse that table still fits, by 2.2 s. No write failed in any in-place build; the 80 ms maximum gap is recorded as measured - the script keeps only the maximum, so its frequency is unknown.
Same laptop and test engines as the premise (PostgreSQL 15.19, ClickHouse 24.8.14.39), load average 1.0-1.4 at the start and 2.6 at the end. Indicative numbers on a shared two-core machine, not a customer qualification.
Docs only; no library change.
🤖 Generated with Claude Code