News for hackers. Stuff that matters.
Re:WasmEdge by azakai on Tuesday November 29, 2022 @05:05PM (#33794033)
Optimizing VMs often use lots of memory for various reasons. Specific costs in modern optimizing VMs include the memory for the JITed code, and with multiple tiers you end up JITing each function more than once. You also need memory to save information about which functions to tier up (a call count or something more refined). Even things like polymorphic inline caches have a cost, the space for each of those PICs, and the code around them.

A simple interpreter can avoid all those. It can build a very simple and compact bytecode and just execute that.

(But, of course, the speedups in optimizing JITs are usually worth it! 10x or more.)

Re:WasmEdge by galangalalgol on Tuesday November 29, 2022 @07:10PM (#33795190)
Does the engine store compiled binaries for the next time the page is loaded?
Re:WasmEdge by azakai on Tuesday November 29, 2022 @07:16PM (#33795239)
Some (most?) do, yes, here is a V8 article on that for example: https://v8.dev/blog/wasm-code-caching
Re:WasmEdge by galangalalgol on Tuesday November 29, 2022 @07:49PM (#33795474)
That seems to imply julia for wasm on chrome wouldn't have the "time to first plot" issue.