syrusakbary
commented
1 week ago Possible solution: add trace logs that show the size of the compiled artifact. Suspicion: if the Wasm module is big, perhaps we are keeping it alive in memory as well as the compiled artifact and that might be adding up on memory
Is there any tool that can show how much memory wasmer used during the loading of the module and the instantiation of the module, on windows I just loaded a simple demo that used more than 500 mb of memory, with the help of vs memory heap analysis I only see a few tens of mb allocated, and with the interfaces under vm/src/mmap.rs there is only 270m, I'm not sure if I can find a tool that can show how much memory was used during the loading and instantiation of the module, but I'd like to know. Where is the rest of the 250+mb memory used?
Translated with DeepL.com (free version)