Realized (yet again) that while events in an emitter may form a DAG, during execution they very much form a tree. This is the same as with regular functions. Any given function may be called by many other functions. But it never has multiple callers simultaneously — so a tree!
Could do differential flame graphs for different versions of the compiler too. See how new runs of the query engine compare to older runs. Also interesting to explore: adding in information about caching, system calls (fs, mostly), plotting flame scopes (to visualize spikes).
-
-
@nnethercote's question of "can we add more tools to look at compiler perf" got me thinking about this. I think this could be an interesting approach to start looking at the compiler from a system level to see if patterns emerge that we can drill down on later.Show this thread -
(I know there is a tracing command available already, but that's only a timeline right now — it's much easier to spot patterns by looking at (sorted) aggregates such as (differential) flamegraphs / flamescopes)
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.