-
Notifications
You must be signed in to change notification settings - Fork 4
docs: update incremental benchmarks (3.4.0) #627
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
carlos-alm
merged 4 commits into
main
from
benchmark/incremental-v3.4.0-20260326-073741
Mar 26, 2026
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
fca7cef
docs: update incremental benchmarks (3.4.0)
github-actions[bot] 93d94fd
Merge branch 'main' into benchmark/incremental-v3.4.0-20260326-073741
carlos-alm 3e19b2e
Merge branch 'main' into benchmark/incremental-v3.4.0-20260326-073741
carlos-alm b05bdd5
Merge branch 'main' into benchmark/incremental-v3.4.0-20260326-073741
carlos-alm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 1-file rebuild time increased +29% for native (346ms → 448ms) and +21% for WASM (508ms → 617ms), but the file count only grew by ~7% (442 → 473 files). For a single-file incremental rebuild the total file count should have minimal impact on latency, so this regression is disproportionate to the codebase growth.
The WASM full build also regressed +15% (4.4s → 5.0s), widening the native/WASM gap from ~1.85× to ~2.21×.
These regressions are faithfully recorded here and the numbers are correct — this is just a heads-up that the underlying performance delta in 3.4.0 may be worth investigating before the next release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Acknowledged — the 1-file rebuild regression (+29% native, +21% WASM) is disproportionate to the ~7% file count growth and worth investigating. Since this is an auto-generated benchmark recording and the numbers are correct, the fix belongs in the codebase (likely in the incremental rebuild path), not in this PR. Will track separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tracked in #635 for follow-up investigation. The regression is real and worth looking into, but as you noted, the benchmark data here is correct — the fix belongs in the incremental rebuild path, not in this docs PR.