You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I suspect that the optimal handling strategy for compute heavy futures will be bimodal:
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.
The text was updated successfully, but these errors were encountered: