Skip to content
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

Clustering for secp256k1 signatures verification #28

Open
skzap opened this issue Aug 27, 2019 · 1 comment
Open

Clustering for secp256k1 signatures verification #28

skzap opened this issue Aug 27, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@skzap
Copy link
Member

skzap commented Aug 27, 2019

Following #20 where I've been able to remove a bottle neck and increase the replay speed, I believe the next big step will be to enable multiple CPU cores usage for the heavy-weight operations that avalon does. So basically I want to do it for the signatures verification, which represent the ultra-majority of the CPU cycles used, and should improve the replay speed a lot for people with 3 cores or more. 2 cores won't change much because mongodb's process is usually already clusterized and will make use of the 2nd core already.

This would greatly improve the replay speed, especially for people using scalable cloud solutions, where it would then be possible to increase your CPU to replay faster, and turning it down once synced.

@skzap skzap added the enhancement New feature or request label Aug 27, 2019
@skzap
Copy link
Member Author

skzap commented Aug 27, 2019

This won't impact the state of the chain (in theory) so it won't have to go through a hardfork either :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant