13 ms·
Well, thank you for pointing out that hierarchical bar charts do a pretty good job at showing the hot path. So my (and I guess your) workflow is then to fix th
by PreInternet01 2y ago
Well, thank you for pointing out that hierarchical bar charts do a pretty good job at showing the hot path.
So my (and I guess your) workflow is then to fix the top-X hot paths, and then re-profile, etc.
The attraction of flame graphs, as I understand it, is that you can get the same information without the need to iterate. Which is obviously very valuable if you're operating on single-shot bug reports, but... how exactly? (Not a question directed at you, obviously, but more towards the general discussion)
- hobs 2y agoI recommend writing your own flame graph generator, the syntax is super simple and it will help you understand the span/subspan nesting. In some cases it's not that helpful if you don't have the right type of problem, eg I was troubleshooting some higher level stuff (SQL) and looking at stored procedure invocations and a two depth invocation doesn't tell you very much. For me a FG is more about sounding out the problem and understanding what the scope of what is possible more than fixing an immediate and obvious issue.
- eterm 2y agoThe jetbrains profiler lets you quickly "Scope to X", so you can scope to the second or third highest ranked functions and see their breakdown too, so you don't need to fix the highest to get a full understanding.