Repository navigation
Rewrite Turbo README around where the speed comes from - #6864
Merged
Merged
Conversation
Move the developer reference into turbo-ext/CLAUDE.md. Amp-Thread-ID: https://ampcode.com/threads/T-01a17d14-ecc8-739d-95cd-95a5056f02ad
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.
The README was out of date (it still said ~25%). It now covers installation, where the speed comes from, how each part works, and why the results stay identical. The developer reference (shadowing mechanics, parity checks, design rules, parser, arena, building, shared core, code style, linting, testing) moved to
turbo-ext/CLAUDE.md. Two outdated sections were dropped: "Performance frontiers", and the build-flags section that claimed PGO no longer helps.Breakdown of the ~58% Turbo saves on PHPStan's analysis of its own
src/, as a share of the time without Turbo:How these were measured:
The analysis output was identical in every configuration.
The chart is a new SVG,
turbo-ext/performance.svg, drawn from the WordPress numbers in the 2.3 release article.