Use a single execution context per wasm interface (per thread) instead of per contract #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
linh2931
added a commit
to AntelopeIO/leap
that referenced
this pull request
Aug 8, 2023
…ution context per wasm interface
heifner
requested changes
Aug 10, 2023
heifner
approved these changes
Aug 10, 2023
spoonincode
approved these changes
Aug 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
A part of eosnetworkfoundation/product#149.
Currently an execution context is created in a
backendobject for each contract, and cached (inside the backend) inwasm_instantiation_cachein the wasm interface object per thread. This wastes physical memory and prevents a single compiled WASM contract code shared across threads.This PR provides an option to decouple execution context from backend, while keeps the existing behavior for backward compatibility.
Resolves AntelopeIO/leap#1456.
API Changes
Documentation Additions