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.

Sign up for GitHub

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

Jump to bottom

Implement a Future using a managed blocker #11051

Open
cody-littley opened this issue Jan 18, 2024 · 0 comments
Open

Implement a Future using a managed blocker #11051

cody-littley opened this issue Jan 18, 2024 · 0 comments
Labels
Good First Issue Either a small change or a medium change concentrated in a single component. Platform Tickets pertaining to the platform

Comments

@cody-littley
Copy link
Contributor

Our future implementations don't work well when you block on them inside a fork join pool. When you block on a future that is implemented using a latch (or equivalent), you end up reducing the maximum concurrency of the pool by 1 until the future is completed.

We should create an implementation of Future that uses a managed blocker paradigm.
@cody-littley cody-littley added the Good First Issue Either a small change or a medium change concentrated in a single component. label Jan 18, 2024
@poulok poulok added the Platform Tickets pertaining to the platform label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Good First Issue Either a small change or a medium change concentrated in a single component. Platform Tickets pertaining to the platform
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cody-littley @poulok