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

Feature: More granular support for types of blocking futures - frequently blocking vs sometimes, long poll vs briefly blocking poll #4

Open
jlizen opened this issue Dec 24, 2024 · 1 comment

Comments

@jlizen
Copy link
Owner

jlizen commented Dec 24, 2024

I suspect that the optimal handling strategy for compute heavy futures will be bimodal:

  • very likely to block, and/or block for a long time
  • occasionally blocking or briefly blocking

For one, it might make more sense to send to a threadpool. The other, maybe something along the lines of block in place or other custom strategies.

It would be good to have an expressive enough API to allow library authors to specify which is which, in case the caller wants to configure strategies separately.

@jlizen jlizen closed this as completed Dec 26, 2024
@jlizen jlizen reopened this Dec 30, 2024
@jlizen
Copy link
Owner Author

jlizen commented Dec 30, 2024

This is no longer quite accurate, but it'd be nice to have in a sync context as well (enabling block-in-place)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant