-
Notifications
You must be signed in to change notification settings - Fork 157
Add triagebot
benchmark
#2145
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 triagebot
benchmark
#2145
Conversation
I profiled this. It looked very normal except for one unusual entry:
The await-call-tree benchmark has 0.7% in that function, and deeply-nested-multi has 0.2%. So there's a quirk, but I don't know if it's enough to justify adding it. We might have spare capacity now, I'd be inclined to keep that available for the inevitable future cases where we want to add a new benchmark for a more compelling reason. |
The original idea was to add a non-trivial real-world app that heavily uses async, because we don't have any of these. But if you think it's uninteresting, we can probably skip it for now, yeah, because it takes a long time to prepare with its 300+ dependencies. FWIW, I tried to switch the config from
and IncrFull:
If you don't see anything interesting there, I'll close this. |
I did a local run with the library, again, it looks similar to before and not that distinctive. |
Ok. Thanks for taking a look! |
Opening as a draft, as an example of a real-world async application.