This repository was archived by the owner on Jun 10, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 110
wasm vm overhead and current state of WASM in browser #699
Unanswered
audacioustux
asked this question in
Q&A
-
Hi.. can someone shade some light on these queries about Lumen and in-general current state of Wasm in browser?
- What's the Lowest runtime overhead of just the Wasm VM and runtime for dummy code, say for C - excluding the initial page size (if has any)
- Lowest startup latency for dummy code, for C
- how many (say for 200B no-op/dummy) wasm modules or vm can be instantiated in per GB memory?
-- in major browsers
The queries kind of irrelevant to Lumen but, as Lumen has done some significant work in this domain, hope to get some feedback on it. What's the lowest overhead and latency Lumen could achieve across browsers in your tests?
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment