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

Recommendations for performance tuning of code running on the tokio runtime #462

Open
nicholasbishop opened this issue Dec 18, 2019 · 1 comment
Labels

Comments

@nicholasbishop
Copy link

As background, I have a couple related services that use async code with the tokio runtime, and the overall throughput just isn't where I would expect it to be. I'm not sure how best to figure out where the performance problems are occurring.

For example, Is there a good way to detect code that is supposed to be async, but instead blocks for a significant amount of time? I've read about the proposal to add a "may_block" attribute to help warn of problems at compile time, but I am also interested in analyzing the runtime behavior of my code to see where it might be blocking.

Looking for async code that is accidentally blocking seems like the most obvious potential source of performance problems, but perhaps there are other things I should be looking for? What tools should I be using to benchmark and profile my async code?

@Darksonn Darksonn transferred this issue from tokio-rs/tokio Jul 25, 2020
@Darksonn Darksonn mentioned this issue Jul 25, 2020
19 tasks
@Darksonn
Copy link
Contributor

Darksonn commented Jul 28, 2020

See tokio#2702.

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

No branches or pull requests

2 participants