source: AE/Setup/Windows/JRE/lib/jvm.hprof.txt@ 869

Last change on this file since 869 was 818, checked in by alloc, 12 years ago

AEI2 Setup Win

File size: 2.7 KB
RevLine 
[818]1Header for -agentlib:hprof (or -Xrunhprof) ASCII Output (JDK 5.0 JVMTI based)
2
3@(#)jvm.hprof.txt 1.5 06/01/28
4
5 Copyright (c) 2006 Sun Microsystems, Inc. All Rights Reserved.
6
7WARNING! This file format is under development, and is subject to
8change without notice.
9
10This file contains the following types of records:
11
12THREAD START
13THREAD END mark the lifetime of Java threads
14
15TRACE represents a Java stack trace. Each trace consists
16 of a series of stack frames. Other records refer to
17 TRACEs to identify (1) where object allocations have
18 taken place, (2) the frames in which GC roots were
19 found, and (3) frequently executed methods.
20
21HEAP DUMP is a complete snapshot of all live objects in the Java
22 heap. Following distinctions are made:
23
24 ROOT root set as determined by GC
25 CLS classes
26 OBJ instances
27 ARR arrays
28
29SITES is a sorted list of allocation sites. This identifies
30 the most heavily allocated object types, and the TRACE
31 at which those allocations occurred.
32
33CPU SAMPLES is a statistical profile of program execution. The VM
34 periodically samples all running threads, and assigns
35 a quantum to active TRACEs in those threads. Entries
36 in this record are TRACEs ranked by the percentage of
37 total quanta they consumed; top-ranked TRACEs are
38 typically hot spots in the program.
39
40CPU TIME is a profile of program execution obtained by measuring
41 the time spent in individual methods (excluding the time
42 spent in callees), as well as by counting the number of
43 times each method is called. Entries in this record are
44 TRACEs ranked by the percentage of total CPU time. The
45 "count" field indicates the number of times each TRACE
46 is invoked.
47
48MONITOR TIME is a profile of monitor contention obtained by measuring
49 the time spent by a thread waiting to enter a monitor.
50 Entries in this record are TRACEs ranked by the percentage
51 of total monitor contention time and a brief description
52 of the monitor. The "count" field indicates the number of
53 times the monitor was contended at that TRACE.
54
55MONITOR DUMP is a complete snapshot of all the monitors and threads in
56 the System.
57
58HEAP DUMP, SITES, CPU SAMPLES|TIME and MONITOR DUMP|TIME records are generated
59at program exit. They can also be obtained during program execution by typing
60Ctrl-\ (on Solaris) or by typing Ctrl-Break (on Win32).
Note: See TracBrowser for help on using the repository browser.