feat(wasix): support direct Node execution - #135
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 11:14
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
execution: "direct"on Node while preserving"worker"as the default@electric-sql/pglite@0.5.4Why
The original Node guard outlived the limitation that motivated it. The runtime can now execute in the caller realm, and an explicit direct placement should be an application choice: it trades worker isolation for lower per-call overhead and can block the caller's event loop. Directory storage keeps its main-thread requirement because its synchronous lease and recovery behavior is a storage constraint, not an execution-placement policy.
Performance evidence
Final commit:
504b40f192570fc13e8096facbb404be4a446f93Matched Node placements, ten alternating fresh-process pairs per placement:
Both gates require
<= 0.80after correctness and PostgreSQL-settings parity. Direct is materially faster on startup, warm round trips, and indexed updates. Bulk insert and index creation remain slower than PGlite and are retained in the gate rather than excluded.The browser qualification already merged into this stack in #134 remains unchanged: direct 0.5035 and worker 0.2029, with workload, durability, and WAL parity passing.
Validation
moon run sdk-contracts:check oliphaunt-js:package oliphaunt-react-native:package oliphaunt-wasix-ts:packagemoon run oliphaunt-wasix-ts:benchgit diff --checkStacked onto the current head of #129 (
f0rr0/wasix-sdk-clean-break).