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
After testing v1.21.0-rc.1 on service deployment - the test mainnet node I found its performance is clearly better than docker deployment
it could be linked to the napi-rs binding #6894 cc @wemeetagain @matthewkeil
Docker deployment should be as great as service deployment's performance
No response
Linux
v1.21.0-rc.1
The text was updated successfully, but these errors were encountered:
could be the performance of aggregateWithRandomness is not the same between service deployment vs docker deployment due to gc
aggregateWithRandomness
gc
Sorry, something went wrong.
closed via the above PR
hash_tree_root() time is always better on service deployment
hash_tree_root()
it's consistent to other types of node. Anyway we're going to go with batch hash which uses a totally different library hashtree #6939
No branches or pull requests
Describe the bug
After testing v1.21.0-rc.1 on service deployment - the test mainnet node I found its performance is clearly better than docker deployment
it could be linked to the napi-rs binding #6894 cc @wemeetagain @matthewkeil
Expected behavior
Docker deployment should be as great as service deployment's performance
Steps to reproduce
No response
Additional context
No response
Operating system
Linux
Lodestar version or commit hash
v1.21.0-rc.1
The text was updated successfully, but these errors were encountered: