News for hackers. Stuff that matters.

A comment on Is WebAssembly magic performance pixie dust? (2021). Parent comment

Re:Is WebAssembly magic performance pixie dust? (2021) by game-of-throws on Thursday July 14, 2022 @05:12PM (#32101526)
The absolute numbers aren't that different. You need 100s of MB just to display an empty Chrome window. Then the 66% is the difference excluding that baseline, e.g. it might be 300MB to load Chrome, then you measure 301MB vs 301.66MB. I guess that might be a bit misleading.

I think the electron memory usage comes down to the massive HTML spec and bloated old browser codebases. It's not JS. Node+V8 doesn't have nearly the memory usage of Chrome+V8.

[ Parent | on HN ]
Re:Is WebAssembly magic performance pixie dust? (2021) by RobbieGM on Thursday July 14, 2022 @06:33PM (#32102202)
That difference is what I'd be interested in anyway as a developer who focuses on PWAs (where the cost of chrome is paid for already). I'm trying to work out whether a WASM stack would help runtime performance, memory usage, and startup time, but based on these numbers it doesn't look so inspiring.
[ Parent | on HN ]