feat: release memory write-ahead VFS 0.2.0#1
Merged
Conversation
Upstream the shared-memory runtime improvements and publish a reproducible PowerSync MemoryVFS comparison. Constraint: Benchmark artifacts compare complete implementation stacks with explicit worker and cache topology. Confidence: high Scope-risk: broad Tested: pnpm prepublishOnly; pnpm test:stress; three benchmark configurations; pnpm audit --prod; npm pack consumer import
whygee-dev
marked this pull request as ready for review
July 14, 2026 21:21
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
Benchmark
In the both-workers comparison, the 3-connection Memory Write-Ahead VFS pool recorded 49.0% lower median concurrent-read latency, 47.6% lower median mixed-read latency, and 75.2% lower median mixed-workload write-completion latency than PowerSync MemoryVFS with one connection. The published artifacts disclose aggregate cache ceilings for every arm; RSS was not measured, so the 3-connection recommendation is throughput-focused rather than memory-balanced.
Validation
pnpm prepublishOnly(format, types, benchmark publisher, 27 browser tests, build)pnpm test:stress(540/540)pnpm audit --prodnpm packplus fresh consumer install/import