Lines Matching full:live
29 <dt><span class="sect2"><a href="dh-manual.html#id534558">10.2.1. Interpreting the max-live, tot-alloc and deaths fields</a></span></dt>
51 <li class="listitem"><p>maximum live volume (number of bytes and
91 <div class="sect2" title="10.2.1.?Interpreting the max-live, tot-alloc and deaths fields">
93 <a name="id534558"></a>10.2.1.?Interpreting the max-live, tot-alloc and deaths fields</h3></div></div></div>
101 max-live: 63,490 in 984 blocks
112 total. By looking at the max-live data, we see that not many blocks
113 were simultaneously live, though: at the peak, there were 63,490
139 max-live: 32,512 in 254 blocks
149 process-lifetime leak. Firstly, the max-live and tot-alloc numbers
165 max-live: 49,398 in 808 blocks
198 max-live: 180,224 in 22 blocks
221 max-live: 54 in 3 blocks
249 max-live: 317,408 in 5,668 blocks
321 <code class="option">--sort-by=<string> [default: max-bytes-live] </code>
329 <p><code class="varname">max-bytes-live </code> maximum live bytes [default]</p>
331 <p><code class="varname">max-blocks-live </code> maximum live blocks</p>
335 by the highest number of live blocks. These give usefully
337 by maximum live blocks tends to show up allocation points
