Lines Matching full:allocation
25 collected and presented per allocation point (allocation
29 <listitem><para>Total allocation (number of bytes and
36 between allocation and freeing)</para></listitem>
41 <listitem><para>for allocation points which always allocate blocks
47 <para>Using these statistics it is possible to identify allocation
111 <para>Over the entire run of the program, this stack (allocation
161 transient allocation-free spike -- rather, it is spread out over a
173 <sect3><title>A fairly harmless allocation point record</title></sect3>
228 simply leaked. So, here is 180k of completely useless allocation that
271 <para>For allocation points that always allocate blocks of the same
358 allocation points according to some metric, and shows the
372 allocation points according to some metric, and shows the
376 <para><varname>tot-bytes-allocd </varname> total allocation (turnover)</para>
378 <para>This controls the order in which allocation points are
379 displayed. You can choose to look at allocation points with
383 by maximum live blocks tends to show up allocation points
390 <para>One important point to note is that each allocation stack counts
391 as a seperate allocation point. Because stacks by default have 12
392 frames, this tends to spread data out over multiple allocation points.
