I was digging this a bit more and it's not the browser but the OS. What Activity Monitor / Task Manager shows is the resident memory. The about:memory page of Firefox clearly shows everything related (resident, vsize, js engine, asm.js, ...).
The questions still apply though. Can I rely on this in practice (given the browser is 64 bit, 32 bit browsers are worse from this point)? Tips for production? 2016. július 26., kedd 15:10:27 UTC+2 időpontban Peter Nemeth a következőt írta: > > I'm trying to find out the best memory configuration for our application. > It's using a lot of user generated content so we cannot be sure about the > required TOTAL_MEMORY at compile time. We could calculate that upfront on > the backend and set in the Module before loading but I would like to avoid > that if possible. Also don't want to enable memory growth because of its > performance drawbacks. After checking some browsers with a simple test it > seems like they are smart enough not to allocate the whole buffer in C++ > regardless the requested size of the ArrayBuffer. Do you know if this works > in practice? How is Emscripten handling the HEAP stack-, and heap-wise? > Where are they located in the HEAP? Any tips from production applications > how they solve memory configuration? > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
