Skip to content
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

refactor: bypass serialized cache in wasmer_wamr flag #119

Closed
wants to merge 1 commit into from

Conversation

mattyg
Copy link
Member

@mattyg mattyg commented Sep 12, 2024

With the wasmer_wamr flag, there is no utility to caching serialized wasms as they are not pre-compiled.

Attempting to use a previously pre-compiled wasm with the flag wasmer_wamr will fail. This could possibly arise if a user caches some wasms to holochain data directory from a holochain conductor with wasmer_sys enabled, and then attempts to use the same data directory in a conductor with wasmer_wamr enabled.

This PR modifies the ModuleCache and SerializedModuleCache to simply bypass actual caching functionality with the feature flag wasmer_wamr

There is no utility to caching serialized wasms as they are not pre-compiled. Attempting to use a previously pre-compiled wasm in the interpreter engine will fail.
@mattyg
Copy link
Member Author

mattyg commented Sep 16, 2024

Closing in favor of a different approach where the caches are not used in holochain, rather than being used but not actually caching.

@mattyg mattyg closed this Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant