Home | History | Annotate | Download | only in docs

Lines Matching full:snapshot

245 represents a snapshot, i.e. a measurement of the memory usage at a certain
246 point in time. If the next snapshot is more than one column away, a
247 horizontal line of characters is drawn from the top of the snapshot to just
248 before the next snapshot column. The text at the bottom show that 25
268 every 10th snapshot is detailed, although this can be changed via the
271 <para>Finally, there is at most one <emphasis>peak</emphasis> snapshot. The
272 peak snapshot is a detailed snapshot, and records the point where memory
273 consumption was greatest. The peak snapshot is represented in the graph by
275 that snapshot 14 was the peak.</para>
282 happens. This avoids lots of unnecessary peak snapshot recordings
339 <sect2 id="ms-manual.thesnapshotdetails" xreflabel="The Snapshot Details">
340 <title>The Snapshot Details</title>
343 information for each snapshot. The first nine snapshots are normal, so only
360 <para>Each normal snapshot records several things.</para>
400 <para>The next snapshot is detailed. As well as the basic counts, it gives
445 the global allocation peak is reached, and a detailed snapshot (number 14)
519 <para>The final detailed snapshot shows how the heap looked at termination.
601 mostly unchanged. One difference is that the start of each detailed snapshot
628 obvious place to start looking is the peak snapshot.</para>
797 and doing a detailed snapshot for every one would be expensive and
824 <option>--detailed-freq=1</option>, every snapshot is
869 <para><varname>snapshot [&lt;filename&gt;]</varname> requests
870 to take a snapshot and save it in the given &lt;filename&gt;
876 requests to take a detailed snapshot and save it in the given