-
-
Notifications
You must be signed in to change notification settings - Fork 255
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 Pprof Profiling to Existing Benchmarks #273
Conversation
Codecov ReportBase: 38.75% // Head: 38.68% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #273 +/- ##
==========================================
- Coverage 38.75% 38.68% -0.07%
==========================================
Files 93 93
Lines 6087 6087
==========================================
- Hits 2359 2355 -4
- Misses 3728 3732 +4
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
The windows failures are because pprof won't compile correctly there. I had to use wsl to compile. Is there something like bench_dependencies for cargo so we can resolve this? Tried googling but didn't find anything |
Actually just found docs |
Do the benchmarks also output a text profile report? |
Not sure I can look into it later in the week. Example flamegraph.svg's from running this are attached. I'll add the relevant one to #262. Let me know if you prefer the proto format, to me it seems more user friendly. |
The zip file only contains the flamegraphs. I guess the profiler doesn't output any extra text right? Also, Criterion still outputs graphs just like before right? As for the format, I still prefer flamegraphs since that's what I'm used to, but ideally I'd like to have both flamegraphs and the proto format. |
As part of this PR, can you also update the Linfa benchmark standards? We should do it once the profiling code is finalized. |
It is one or the other you either output flamegraphs or use criterion as the measurement method. See here for documentation evidence. As for the format I believe it is either flamegraph format or proto format. I don't think you can do both without running the benchmark twice. Not a problem to add just not sure if the value add is worth it. |
yep once we agree on this PR being ready for merge I plan to. |
Resolves #272.
By the way running the benchmarks in the background and will update #228 once if this is approved.