Refactor instance to avoid keeping a copy of Module#233
Conversation
|
@gumb0 should I rebase this or drop it? |
|
I think the only things we could discard in So maybe not worth it. |
|
|
|
This is made a bit more challenging with #281. Closing. |
|
I was considering copying only required part of the module to the instance, but that would include all the code should be the biggest part of the module. Moreover, freeing the module is not beneficial short-term. Freeing actually cost you time. Can we close this? |
The code isn't the biggest, the data segment is the biggest, which is already copied. |
|
None of our benchmarks has bigger Data than Code. |
|
The data section contains a sparse description of the memory. In many cases it is expanded to a larger output than the encoded version. |
|
Rather outdated PR by now. |
No description provided.