-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Feature Request: profile
output should be sorted
#7638
Comments
The downside of that is it would make the ordering unstable from run to run, making comparisons difficult. Currently it's in rough order of realization, which is also annoying, because it's sensitive to the schedule. Possibly it should be in pipeline order, so early stages are always at the top, and later stages are always at the bottom. |
True, but usually when I'm profiling I want to start by looking at the biggest costs; this makes them easier to spot. (Maybe consider adding it via an env var?)
Is that information transmitted to the profiler right now? if not, how hard would it be? |
Fixes halide#7638) (halide#7639) * Allow optional sorting of profiler output via HL_PROFILER_SORT env var (Fixes halide#7638) * trigger buildbots * Update profiler_common.cpp * Update float16_t.cpp * Update float16_t.cpp * Update float16_t.cpp * Update float16_t.cpp
It would be a bit easier to read the
profile
output ifhalide_profiler_report_unlocked()
sorted the output by percentage.The text was updated successfully, but these errors were encountered: