-
Notifications
You must be signed in to change notification settings - Fork 3
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
Enable greater parallelization of concurrent WASM executions #149
Comments
3 tasks
bhazzard
changed the title
Proposal: Parallelized Reads memory issues
Identify memory issues caused by parallelized reads
Apr 21, 2023
This was referenced May 11, 2023
8 tasks
bhazzard
changed the title
Identify memory issues caused by parallelized reads
Enable greater parallelization of concurrent WASM executions
Jun 8, 2023
bhazzard
modified the milestones:
Leap v5.0.0 Sep/Oct 2023,
Leap v5.0.0 Cusp Sep/Oct 2023
Jul 11, 2023
2 tasks
@bhazzard and @stephenpdeos can you review Lin's document and provide next steps? Thanks. |
This was referenced Aug 23, 2023
Closed. All tasks assigned to @linh2931 were completed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parallelization of read only transactions is limited by the number of concurrent WASM executions that can be supported by Leap. There are resource limits that bound the number of concurrent WASM executions allowed. This epic focusses on changes to eos-vm runtimes (for example: interpreter, JIT, and OC), as well as further optimizations within Leap to increase the number of concurrent WASM executions that Leap can support.
Tasks
The text was updated successfully, but these errors were encountered: