<story><title>QDirStat – Treemap Visualization of Directory Statistics</title><url>https://github.com/shundhammer/qdirstat</url></story><parent_chain><item><author>vilya</author><text>Gosh there are a lot of these programs, aren&amp;#x27;t there?&lt;p&gt;For some reason I find it really hard to read these tree map visualisations. I know the theory and all that, but for me they just aren&amp;#x27;t an intuitive way of displaying that kind of information. For me a radial graph (i.e. pie chart like) is much easier to grok - I don&amp;#x27;t even have to think about it, I just get it. Seems like there must be plenty of people who don&amp;#x27;t think the same way though, given how many different tree map disk viewers there are out there!&lt;p&gt;For what it&amp;#x27;s worth I use Diskitude (&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;madebyevan.com&amp;#x2F;diskitude&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;madebyevan.com&amp;#x2F;diskitude&amp;#x2F;&lt;/a&gt;) on Windows and Daisy Disk (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;daisydiskapp.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;daisydiskapp.com&amp;#x2F;&lt;/a&gt;) on Mac. Both are great!</text></item></parent_chain><comment><author>chubot</author><text>I&amp;#x27;ve used treemaps for many years, to reduce disk space, and have been somewhat enamored of them.&lt;p&gt;Then earlier this year, I happened to use flame graphs for visualizing profiling data.&lt;p&gt;This is when I realized I hadn&amp;#x27;t quite understood flame graphs.  It became obvious that you can use flame graphs for visualizing the SPACE used by a tree hierarchy as well as TIME.&lt;p&gt;I googled and Brendan Gregg already wrote about this!&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.brendangregg.com&amp;#x2F;blog&amp;#x2F;2017-02-05&amp;#x2F;file-system-flame-graph.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.brendangregg.com&amp;#x2F;blog&amp;#x2F;2017-02-05&amp;#x2F;file-system-flam...&lt;/a&gt;&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.brendangregg.com&amp;#x2F;blog&amp;#x2F;2017-02-06&amp;#x2F;flamegraphs-vs-treemaps-vs-sunburst.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.brendangregg.com&amp;#x2F;blog&amp;#x2F;2017-02-06&amp;#x2F;flamegraphs-vs-t...&lt;/a&gt;&lt;p&gt;So from now on, I believe I will use flame graphs instead of treemaps to visualize this space.&lt;p&gt;-----&lt;p&gt;Details:  A common point of confusion for flame graphs is that the Y axis is &amp;quot;time elapsed&amp;quot;.  (Chrome dev tools has a &amp;quot;flame chart&amp;quot; where the Y axis is time elapsed, but it&amp;#x27;s not a flame graph.)&lt;p&gt;The Y axis is &amp;quot;cumulative time used&amp;quot;, and the X axis is the call stack.  Combining call stacks sampled at different times gives you a TREE, because a given function calls multiple functions.&lt;p&gt;So if that&amp;#x27;s clear, it should be clear why flame graphs can be used instead of treemaps.  They are the same visualization!  And flame graphs have the benefit that they use a one spatial dimension to represent quantity, rather than two.  TreeMaps have the same problem as pie charts -- human perception isn&amp;#x27;t good at measuring areas.&lt;p&gt;Also, with treemaps, you have error due to the inability to represent a internal directory of zero size (you need some space for the label).  Flame Graphs don&amp;#x27;t have this problem because directories are stacked on the Y axis.</text></comment>
<story><title>QDirStat – Treemap Visualization of Directory Statistics</title><url>https://github.com/shundhammer/qdirstat</url></story><parent_chain><item><author>vilya</author><text>Gosh there are a lot of these programs, aren&amp;#x27;t there?&lt;p&gt;For some reason I find it really hard to read these tree map visualisations. I know the theory and all that, but for me they just aren&amp;#x27;t an intuitive way of displaying that kind of information. For me a radial graph (i.e. pie chart like) is much easier to grok - I don&amp;#x27;t even have to think about it, I just get it. Seems like there must be plenty of people who don&amp;#x27;t think the same way though, given how many different tree map disk viewers there are out there!&lt;p&gt;For what it&amp;#x27;s worth I use Diskitude (&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;madebyevan.com&amp;#x2F;diskitude&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;madebyevan.com&amp;#x2F;diskitude&amp;#x2F;&lt;/a&gt;) on Windows and Daisy Disk (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;daisydiskapp.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;daisydiskapp.com&amp;#x2F;&lt;/a&gt;) on Mac. Both are great!</text></item></parent_chain><comment><author>jdonaldson</author><text>There&amp;#x27;s a few reasons why rectangular shapes are superior... They fill the available space better than circles, and you can generally compare areas in rectangular shapes better than areas with curves.  But, generally you&amp;#x27;re using these tools to spot outliers, in which case either approach works just fine.</text></comment>