Skip to content

WASM executor pool #1453

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

Open
iduartgomez opened this issue Mar 8, 2025 · 0 comments · May be fixed by #1494
Open

WASM executor pool #1453

iduartgomez opened this issue Mar 8, 2025 · 0 comments · May be fixed by #1494
Assignees
Labels
A-contract-runtime Area: contract execution and runtime C-optimization Category: An optimization over an existing functionality. E-medium Experience needed to fix/implement: Medium / intermediate

Comments

@iduartgomez
Copy link
Collaborator

  • Multi-thread wasm executor. Add a job stealing pool of runtimes at the executor for wasm contracts. Make sure that we don’t run updates in parallel for the same ContractInstanceId.
    • We don’t have to block threads (like we are currently doing) when running the runtime functions (example validate_stateetc).
    • Those can be ran in a different task and as we complete them send the result back.
    • Check crates/core/src/contract.rs contract_handling function, here is where we get the requests for running on the contracts that we would have to run in parallel.
@iduartgomez iduartgomez moved this to In Progress in Freenet Core Mar 8, 2025
@iduartgomez iduartgomez self-assigned this Mar 8, 2025
@iduartgomez iduartgomez added C-optimization Category: An optimization over an existing functionality. A-contract-runtime Area: contract execution and runtime E-medium Experience needed to fix/implement: Medium / intermediate labels Mar 8, 2025
@iduartgomez iduartgomez linked a pull request Mar 23, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-contract-runtime Area: contract execution and runtime C-optimization Category: An optimization over an existing functionality. E-medium Experience needed to fix/implement: Medium / intermediate
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

1 participant