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

Add documentation note that future_queue (and buffer_unordered) don't limit concurrency in certain cases #1

Open
sunshowers opened this issue Dec 28, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@sunshowers
Copy link
Member

These limit the number of concurrently running futures, which often but doesn't always limit overall concurrency. Add a note about this.

From @hawkw:

if your stream is returning tokio::spawn(do_stuff()) and you group them into a queue, the concurrency isn't limited, but if your stream is returning async move { tokio::spawn(do_stuff()).await } then the task isn't spawned until the future is actually polled for the first time

@sunshowers sunshowers added the documentation Improvements or additions to documentation label Dec 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant