-
Notifications
You must be signed in to change notification settings - Fork 105
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(sandbox-host): Process wasm-globals on wasmer side #2969
Conversation
from Benchmarks 84 - https://github.com/gear-tech/gear/actions/runs/5635224234
|
blocked by #2948 |
I guess it's a part of #1771? |
Nope, 1771 is a different approach involving modified instrumentation. |
Conflicts: core-backend/common/src/funcs.rs core-backend/sandbox/src/env.rs core-backend/sandbox/src/runtime.rs core-backend/wasmi/src/runtime.rs
from benchmarks 88 - https://github.com/gear-tech/gear/actions/runs/5784482295
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!
Resolves #2920
@gear-tech/dev
Release notes: This PR introduces processing of WASM-globals on execution backend side (namely wasmer). The approach allows to eliminate redundant host-calls (what is expensive in terms of gas consumption) to get/set the binary globals during execution of a program. The benchmarks show syscalls gas reducing on 30% in average, up to 90% at most.