Open itamarst opened 2 years ago
I agree, although I also suspect this'll be quite tricky to fix in chart mode. You'd need a sort of two-pass thing where we first scan for how expensive each function is in aggregate (by basically doing a non-chart plot and now drawing it), and then carrying that information forward into chart mode.
Yeah, or a trie-like thing.
Consider the following profiling result:
In flamegraph mode with
--colordiffusion
, the bottleneck is darker red, since it is 60% of time spent vs 40%:In flamechart mode, however, the segments all have the same red saturation:
Insofar as the goal of the color mode is to highlight more significant parts of the code, this is wrong: the relative saturation should be the same as in the flamegraph. Just because the bottleneck is chopped up doesn't mean it has ceased to be the bottleneck, it should still be redder.