-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
question about blocking action? #2417
Comments
async-std's runtime can not detect blocking calls automatically too AFAIK. That pull request from the blog post was closed. |
Hi. You might want to read this quite recent documentation improvement, which should address these questions. The question is also addressed in this blog post, which also explains why async-std's proposed blocking-detection is not comparable to what golang does. So the answer is: You need to continue using I am closing this issue, but feel free to post additional questions here. |
no , do you see async-rs/async-std#733 #631 PR is a successor impl in #733 . and it is merged. |
Hi, async_std is successful impl this PR. |
Tokio does not have any plans to implement such a feature due to its detrimental effects on the tail latencies of the system. The blog post I linked explains why in the “A note on blocking” section. |
My understanding is that the PR you linked (async-rs/async-std#733) does not contain the automatic detection of blocking operations, only internal refactors to the async-std runtime that were factored out from async-rs/async-std#631. See async-rs/async-std#631 (comment):
And async-rs/async-std#733 (comment)::
|
If I want to run a blocking action, do I need to manually differentiate? Can you automatically To deal with?
allow replace to Auto deal with
Because there are many libraries many IO operations are blocked for historical reasons(Even rust Std libraries)
If you use manual differentiation, you'll end up with a huge amount of code。
“async_std” this crate can auto(Inspired by golang), for example doc.
https://async.rs/blog/stop-worrying-about-blocking-the-new-async-std-runtime/
The text was updated successfully, but these errors were encountered: