Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
This repository was archived by the owner on Jun 10, 2024. It is now read-only.

wasm vm overhead and current state of WASM in browser #699

Unanswered
audacioustux asked this question in Q&A
Discussion options

Hi.. can someone shade some light on these queries about Lumen and in-general current state of Wasm in browser?

  1. 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)
  2. Lowest startup latency for dummy code, for C
  3. 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?

You must be logged in to vote

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant

AltStyle によって変換されたページ (->オリジナル) /