We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Proposal: reduce memory allocations in tx execution
Current behavior:
When benchmark parallel EVM execution, memory allocation, and GC seem becoming a bottleneck.
And there are indeed many unnecessary allocations in both SDK and ethermint
Desired behavior:
Pick some low hanging fruits first:
Use case: [Why is this important (helps with prioritizing requests)]
Requests may be closed if we're not actively planning to work on them.
GetAccount
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Proposal: reduce memory allocations in tx execution
Current behavior:
When benchmark parallel EVM execution, memory allocation, and GC seem becoming a bottleneck.
And there are indeed many unnecessary allocations in both SDK and ethermint
Desired behavior:
Pick some low hanging fruits first:
Use case: [Why is this important (helps with prioritizing requests)]
Requests may be closed if we're not actively planning to work on them.
Tracking
GetAccount
callsThe text was updated successfully, but these errors were encountered: