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

Do not create/use/cache execution context per contract #1456

Closed
Tracked by #149
linh2931 opened this issue Jul 27, 2023 · 0 comments · Fixed by AntelopeIO/eos-vm#19 or #1484
Closed
Tracked by #149

Do not create/use/cache execution context per contract #1456

linh2931 opened this issue Jul 27, 2023 · 0 comments · Fixed by AntelopeIO/eos-vm#19 or #1484
Assignees

Comments

@linh2931
Copy link
Member

A part of eosnetworkfoundation/product#149.

Currently an execution context is created/used/cached per contract. Towards our goal of sharing the same compiled WASM code across all the threads, we need to make an execution context per thread (or wasm interface). A good side effect of this is memory usage reduction since execution context per contract is not cached any more in physical memory in running nodeos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment