perf(wasix): qualify browser benchmarks - #134
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
f0rr0
marked this pull request as ready for review
August 13, 2026 09:52
f0rr0
added a commit
that referenced
this pull request
Aug 13, 2026
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
Adds qualified browser performance evidence as a minimal follow-up to merged #133, stacked directly on the current #129 head.
@electric-sql/pglite@0.5.4<= 0.80geometric-mean ratio independently in both browser topologies so one cannot subsidize the otherThe old every-metric 30% rule was brittle for sub-millisecond operations and overweighted insert diagnostics. This gate is not a weaker semantic comparison: workload assertions, cross-origin isolation, PostgreSQL durability settings, and indexed-insert WAL parity must pass before either topology can qualify. Cold first open, duplicated workload-open time, close, and insert decomposition remain visible but descriptive; close is excluded because the public APIs make different worker-reclamation guarantees.
Full browser result
The qualifying run is bound to clean commit
3972f98c9666e83ee2b4a4f42d8389d9702b17caand plan digest89c2d4fe5c32c1d8593243578742404fcf7e8b4661cc40398ce953233b186493.25d0a55e1f1e4c59f26d9e125150dda88a33fd00b3925de04c386f51859c1bf18c143b225e3850616718140dd32e8eb48e9a2c841.0in both topologiesReproduce with:
or write to an explicit directory:
Validation
Base: #129 at
94854946681109552871f3d49aa2e740779882c5.