Repository navigation
perf(PERF-01): measure compiled payload and browser worker costs - #37
Merged
Merged
Conversation
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.
Closes #26.
Measure the existing dependency-selected helpers against all helpers available to the same compiler profile. A reproducible report separates source, generated modules, helpers, maps, notices, metadata/harness, complete payload, per-file gzip and canonical compressed archives. It records warm compiler builds, fresh/warm browser-context startup, and separate dedicated-worker V8 heap observations with actual tool/source/corpus identities and raw samples.
Both helper modes must match the 24-case CPython corpus in Node and Chromium; deliberately corrupting arithmetic demonstrates that two wrong variants cannot satisfy the reference gate. Three measured fixtures each cover both helper modes and source-map policies. The checked-in five-sample observations describe synchronous compiler fixtures, including their measurement harness; browser-host/PWA shells and future interpreter comparisons remain separate. Compiler runtime code, language behavior, dependency versions and package release version are unchanged.
Validation: 85 tests; three measurement tests against an isolated built wheel; 48 corpus observations per JavaScript target; twelve browser fixtures with five build/cold/warm/heap samples per condition. CI pins the browser job's Node version and retains its fresh measurement report. No general speed or memory improvement is claimed.