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

Avoid rayon in lighthouse block verification #5992

Merged
merged 1 commit into from
Jun 27, 2024

Conversation

pawanjay176
Copy link
Member

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.

Copy link
Member

@michaelsproul michaelsproul left a 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

@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. v5.3.0 Q3 2024 release with database changes! labels Jun 27, 2024
@michaelsproul
Copy link
Member

@Mergifyio queue

Copy link

mergify bot commented Jun 27, 2024

queue

🛑 The pull request has been removed from the queue default

The queue conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

mergify bot added a commit that referenced this pull request Jun 27, 2024
@michaelsproul
Copy link
Member

@Mergifyio queue

Copy link

mergify bot commented Jun 27, 2024

queue

🛑 The pull request has been removed from the queue default

The queue conditions cannot be satisfied due to failing checks.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

@jimmygchen
Copy link
Member

@mergify requeue

Copy link

mergify bot commented Jun 27, 2024

requeue

✅ This pull request will be re-embarked automatically

The followup queue command will be automatically executed to re-embark the pull request

Copy link

mergify bot commented Jun 27, 2024

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at f106533

mergify bot added a commit that referenced this pull request Jun 27, 2024
@mergify mergify bot merged commit f106533 into sigp:unstable Jun 27, 2024
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge This PR is ready to merge. v5.3.0 Q3 2024 release with database changes!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants