#366·wasm3

Clone a parsed module that has not been loaded to a runtime

Author: reuvenpoCreated Aug 14, 2022Updated Sep 14, 2026
LabelsfeatureAPI

When running very short workloads, the time spent in the m3_ParseModule can be significant, or even most of the execution time. This can be mitigated by being able to save a parsed module, and then only call m3_LoadModule on deep copies of it.

Reusing the runtime is not an option because I have many modules with the same interfaces, and state can not be allowed to "leak" between runs of modules, even if the same module is run twice.