[draft][wasm] Memory snapshot

[maraf]

• Use node to take memory snapshot using standard mono-config.json after build,
• Use wa-edit to merge the snapshot into dotnet.wasm,
• Override config for sample & library to use only dotnet.wasm
• The final appbundle now consists of dotnet.js and dotnet.wasm
• -p:WasmMemorySnapshotClearUnmanaged=false disables zeroing-out unmanaged memory on free. Snapshot will be slightly larger (~40KB), but increases speed. In the end, we would have to use different build for snapshot and for runtime
• -p:WasmMemorySnapshotNodeExecutable enables to switch to node different from emsdk

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

• Use node to take memory snapshot using standard mono-config.json after build,
• Override config for sample & library tests to use memory snapshot.

Author:	maraf
Assignees:	maraf
Labels:	NO-MERGE, arch-wasm, area-System.Runtime.InteropServices.JavaScript
Milestone:	-

[maraf]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Draft Pull Request was automatically closed for 30 days of inactivity. Please let us know if you'd like to reopen it.

[pavelsavara]

@maraf
Here are some interesting ideas https://github.com/bytecodealliance/wizer/

• use wasm-opt after taking snapshot to make it smaller and shake out the code which was only necessary for initialization!