News for hackers. Stuff that matters.

A comment on Lucet: Native WebAssembly Compiler and Runtime. Parent comment

Re:Lucet: Native WebAssembly Compiler and Runtime by acqq on Friday March 29, 2019 @03:15PM (#19524631)
> Loading code into the runtime is fast because its mostly a call to `dlopen

Does that mean that you measure only loading and not the compilation and verification in your “50 ms” time?

[ Parent | on HN ]
Re:Lucet: Native WebAssembly Compiler and Runtime by phickey on Friday March 29, 2019 @04:35PM (#19525410)
Instantiation takes under 50 microseconds (us) on the lab machine I tested on, and 65us on my colleague's laptop. Loading the code takes about that long as well (see thread: https://twitter.com/acfoltzer/status/1111387279434485760). Compilation is not counted towards any of those tallies.

In our use case, we do compilation on a control plane system and distribute the shared object file to the fleet, so we aren't too concerned by it. For applications where compilation time is a bigger concern, I'm super impressed by this (still early) work on a one-pass wasm compiler: https://github.com/CraneStation/lightbeam

[ Parent | on HN ]
Re:Lucet: Native WebAssembly Compiler and Runtime by acqq on Sunday March 31, 2019 @06:49PM (#19538952)
> 50 microseconds

Yes, sorry for my error in writing, of course, 50 ms would be only 20 times per second. Thanks a lot for your explanations.

[ Parent | on HN ]
Re:Lucet: Native WebAssembly Compiler and Runtime by smjain on Wednesday April 03, 2019 @03:48AM (#19561575)
so do we keep a pool of VMs with the so file loaded already and instantiate only the module on demand which means allocation of memory and setup of other data structures
[ Parent | on HN ]