wasm vm overhead and current state of WASM in browser

[audacioustux]

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?