-
Notifications
You must be signed in to change notification settings - Fork 804
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
Avoid rayon in lighthouse block verification #5992
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rayon getting deleted. I love to see it.
Agree we should just merge this to unstable rather than fitting it into 5.2.1
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
@mergify requeue |
✅ This pull request will be re-embarked automaticallyThe followup |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at f106533 |
Issue Addressed
N/A
Proposed Changes
The blst library's
verify_multiple_aggregate_signatures
function already spreads the verification across multiple cores, we are doing redundant parallelization in lighthouse.This PR just calls the blst function directly without doing any additional parralelization.
I'm guessing we did this when we were also using milagro bls as it presumably didn't parallelize, but now that we exclusively use blst, this is not needed anymore.
Additional info
This PR need not necessarily be in 5.2.1, we can get some additional long term testing for this to check it doesn't result in performance degradation somehow.