An integration + optimization code I’m working on generates flame graphs like this one, which are very hard to parse. Indeed, the same underlying function is called by several different lines of the code, so even if I spend lots of time in it, this time is spread across the many columns of tiles.
Is there a way to get rid of the call stack hierarchy and instead group by function? Or do I have to use the text-based Profile interface instead?
1 Like
I think the answer is to group sections of code with
I think this is just a limitation of FlameGraphs. Personally, to get around this I tend to use VSCode’s inbuilt profiler which annotates the source code itself with time spent thereby grouping by source line. Alternatively, I think StatProfileHTML or PProf can group by function.
What do you mean by the built-in profiler?
Sorry, I meant this Profiler · Julia in VS Code (julia-vscode.org). The thing you get when you use @profview in the REPL.
1 Like