refactor(benchmarks): isolate canonical workload examples - #17
Merged
thejustinwalsh merged 3 commits intoAug 4, 2026
Merged
Conversation
thejustinwalsh
force-pushed
the
feat/benchmark-workload-examples
branch
from
August 4, 2026 01:44
01a4941 to
c07c7d3
Compare
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.
Summary
Textconstruction into a dedicatedapps/benchmarks/src/workloads/example moduleArchitecture
The seven comparison workloads now read as package-consumer examples: Text Ladder, Zoom Text, Icon Grid, Off-axis 3D, Dynamic Layout, Paragraph Stress, and Paint & Effects each visibly construct public
@pmndrs/textTextobjects in their own module.renderer/comparison-workload.tsremains the generic retained-scene adapter and contains nonew Text(...)calls.Low-level targets now live under
benchmark/targets/product,measurement, andconformance.benchmark/targets.tsis a two-line lazy facade. A deterministic boundary test allowlists direct font-baker/Wasm imports to one low-level dependency adapter and resolves every registered target ID.This changes benchmark application structure only. It does not add a public package API, change runtime/baker/Wasm artifacts, or change renderer ownership.
Verification
pnpm benchmarks:check— 271 unit tests, lint, formatting, production build, and exact package-size checks passedpnpm --filter @pmndrs/text-benchmarks test— complete size, autoresearch, bidi/CJK contract, unit, headless conformance, and packed-consumer suite passedpnpm benchmarks:check:react-doctor— no issues foundpnpm docs:check— zero conformance, producer-profile, or warning findingsReview note
The React viewport remains a single generic host adapter in
app.tsx; creating seven wrapper components would duplicate route/loading/evidence plumbing without making the library examples clearer. The existing host-facing optional entry view remains isolated behind the new factories; replacing it with seven exact runtime-state unions is intentionally outside this behavior-preserving structure change.