Skip to content

use block_current_stream work api #241

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

Closed
wants to merge 2 commits into from

Conversation

tushar00jain
Copy link
Contributor

@tushar00jain tushar00jain commented Jul 24, 2025

Summary:

  • use block_current_stream to avoid blocking the cpu when using gloo

Stack created with Sapling. Best reviewed with ReviewStack.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Meta Open Source bot. label Jul 24, 2025
@tushar00jain tushar00jain marked this pull request as draft July 24, 2025 21:56
Summary:
- we current wait for pg work's future when preparing for a fragment
- if we use gloo, this blocks the cpu
- move the wait call to when we perform the actual sync of the fragment
- use http transport instead of pg transport -- pg transport fails to resolve address when running locally
Summary:
- use block_current_stream to avoid blocking the cpu when using gloo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Meta Open Source bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants