fix(benchmarks): measure eager RSC entry closure#2208
Merged
james-elicx merged 1 commit intoJun 20, 2026
Conversation
commit: |
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
2 participants
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 RSC benchmark previously measured only
index.js, so chunk rebalancing could look like a regression. It now includes all eager static imports while excluding lazy chunks and external dependencies. This correctly shows PR #2206 reducing the RSC entry closure from 98.7 KB to 94.3 KB gzip.CI failing due to touching benchmarks from a fork.
@james-elicx after merging this, can you calc values for the last 100 commits again (also for the other stats that dont have full value coverage yet)?