-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Wasmer] Remove serialized module cache #3536
Open
Comments
This item has been open for 30 days with no activity. |
github-actions
bot
added
the
stale
This issue may be outdated, but we can revive it if it ever becomes relevant again
label
May 4, 2024
abe-njama
removed
the
stale
This issue may be outdated, but we can revive it if it ever becomes relevant again
label
May 10, 2024
This item has been open for 30 days with no activity. |
github-actions
bot
added
the
stale
This issue may be outdated, but we can revive it if it ever becomes relevant again
label
Jun 10, 2024
abe-njama
removed
the
stale
This issue may be outdated, but we can revive it if it ever becomes relevant again
label
Jun 11, 2024
This item has been open for 30 days with no activity. |
github-actions
bot
added
the
stale
This issue may be outdated, but we can revive it if it ever becomes relevant again
label
Jul 12, 2024
abe-njama
added
permanent
Exempt this item from being marked stale and closed.
and removed
stale
This issue may be outdated, but we can revive it if it ever becomes relevant again
labels
Jul 17, 2024
jost-s
removed
the
permanent
Exempt this item from being marked stale and closed.
label
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
holochain_wasmer
has three caches:The in-memory cache of serialized modules is redundant. If the module is not in the deserialized cache, which is the fastest way to obtain an executable module, it can either be found on the file system or needs to be compiled from wasm. There's no need to store it in serialized form in-memory.
The text was updated successfully, but these errors were encountered: