News for hackers. Stuff that matters.
Re:A 40-line fix eliminated a 400x performance gap by wging on Tuesday January 13, 2026 @09:53PM (#46611696)
I also like icicle graphs for this. They're flamegraphs, but aggregated in the reverse order. (I.e. if you have calls A->B->C and D->E->C, then both calls to C are aggregated together, rather than being stacked on top of B and E respectively. It can make it easier to see what's wrong when you have a bunch of distinct codepaths that all invoke a common library where you're spending too much time.)

Regular flamegraphs are good too, icicle graphs are just another tool in the toolbox.

Re:A 40-line fix eliminated a 400x performance gap by pests on Wednesday January 14, 2026 @01:27AM (#46612990)
So someone else linked the original flamegraph site [0] and it describes icicle graphs as "inverting the y axis" but that's not only what's happening, right? You bucket top-down the stack opposed to bottom-up, correct?

[0] https://www.brendangregg.com/flamegraphs.html

Re:A 40-line fix eliminated a 400x performance gap by yxhuvud on Wednesday January 14, 2026 @05:51AM (#46614534)
Right, what is needed is something trie-like, with the root being the most fine-grained call.
Re:A 40-line fix eliminated a 400x performance gap by wging on Wednesday January 14, 2026 @01:20PM (#46620049)
It's certainly possible that what I encountered, labeled as an 'icicle graph', is a nonstandard usage of the term. But if so, that's a shame. I don't think inverting the y-axis is useful by itself, the different bucketing is what makes for an actually useful change.