Lines Matching full:program
18 program uses. This includes both the useful space, and the extra bytes
20 measure the size of your program's stack(s), although it does not do so by
23 <para>Heap profiling can help you reduce the amount of memory your program
28 <listitem><para>It can speed up your program -- a smaller
29 program will interact better with your machine's caches and
32 <listitem><para>If your program uses lots of memory, it will
45 program is using, it also gives very detailed information that indicates
46 which parts of your program are responsible for allocating the heap memory.
57 matter much what optimisation level you compile your program with, as this
67 <title>An Example Program</title>
69 <para>An example will make things clear. Consider the following C program
114 <para>To gather heap profiling information about the program
120 <para>The program will execute (slowly). Upon completion, no summary
140 the program's execution, and (b) detailed information about the responsible
141 allocation sites at various points in the program, including the point of
153 <para>After running this program under Massif, the first part of ms_print's
154 output contains a preamble which just states how the program, Massif and
172 as the program executed:</para>
206 instructions involve the loading and dynamic linking of the program. The
208 allocations) only occur at the very end. For a short-running program like
213 <para>If we re-run the program under Massif with this option, and then
249 snapshots were taken for this program, which is one per heap
251 snapshots for every heap allocation/deallocation, but as a program runs for
253 snapshots as the program goes on; when it reaches the maximum number of
267 snapshots were taken for this program (snapshots 9, 14 and 24). By default,
283 (imagine what happens if your program allocates a lot of heap blocks in
285 program never deallocates any blocks, no peak will be recorded. It also
286 means that if your program does deallocate blocks but later allocates to a
373 program.</para></listitem>
376 This reflects the number of bytes allocated in excess of what the program
457 point in the program into a single tree, which gives a complete picture at
537 <para>If your program forks, the child will inherit all the profiling data that
571 memory, and then hand over pieces of that memory chunk to the client program
578 Furthermore, a client program may use these lower-level system calls
582 tools such as <filename>top</filename> that measure a program's total size in
588 your program, you can use the <option>--pages-as-heap=yes</option>. When this
617 them may require some detailed understanding of the lower levels of a program
687 stack that a user program actually has control over.</para>
