|
The JRockit Runtime Analyzer (JRA) system consists of two parts (Figure 1-1): one part inside the JRockit JVM that collects and saves data (the JRA recording engine); and an analysis tool that visualizes the information (JRA Tool). The JRockit-internal part produces a recording of the system's runtime behavior during a user specified period of time, typically a few minutes. The recording results in an XML file that is automatically transferred to Mission Control and opened in the JRA Tool (this behavior is valid for JRockit 5.0 and later; for JRockit 1.4, the file is saved locally to disk and you need to locate it before opening the file).
The recording is a great way to share how JRockit has worked with your application. You can also use several recordings to compare and contrast how different command line options change the behavior of your application, for example, by creating before-and-after recordings. When sending trouble reports to the BEA JRockit support department, you are required to attach a JRA recording to your trouble report. The recording is analyzed "offline" by the JRockit Runtime Analyzer Tool.
The recording engine uses several sources of information including the JRockit Hot Spot Detector (also used by the optimization engine to decide what methods to optimize), the operating system, the JRockit Memory System (most notably the garbage collector), the JRockit thread analyzer (if enabled), and the JRockit lock profiler (if enabled).
|
|