-
Notifications
You must be signed in to change notification settings - Fork 957
Run reconstruction inside a scoped rayon pool #8075
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
Run reconstruction inside a scoped rayon pool #8075
Conversation
…ckfill-verify-kzg-use-scoped-rayon
…ckfill-verify-kzg-use-scoped-rayon
…ckfill-verify-kzg-use-scoped-rayon
…ckfill-verify-kzg-use-scoped-rayon
….com/jimmygchen/lighthouse into backfill-verify-kzg-use-scoped-rayon
…ckfill-verify-kzg-use-scoped-rayon
jimmygchen
left a comment
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.
Hey @eserilev I think your suggested approach looks good and i don't see any issue with it.
|
Updating this to |
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.
Looking good, thanks! Will wait for another reviewer and some testing and then merge this.
I think it might be worth clarifying on the below functions, i.e. the difference isnt just blocking /async, we'd use the 2nd one of if we want to block the async thread to await for the return values (maybe fn naming + describe when to use each?)
spawn_blocking_with_rayonspawn_rayon_async
jimmygchen
left a comment
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.
Nice numbers 👏 pretty good improvements there, shows that the scoped rayon impl is quite effective.
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks: You can check the last failing draft PR here: #8107. You may have to fix your CI before adding the pull request to the queue again. |
Co-Authored-By: Jimmy Chen <[email protected]> Co-Authored-By: Eitan Seri- Levi <[email protected]> Co-Authored-By: Eitan Seri-Levi <[email protected]>






spawn_blocking_handle_with_rayonfn insideTaskExecutor.RayonManagerreference toTaskExecutorIt isn't straightforward to convert the full Reconstruction work event from an async to a blocking task. This approach is a temporary stopgap until we are able to fully separate async tasks from compute heavy tasks.