Admin: Graphs
From Resin 3.0
| Line 39: | Line 39: | ||
The JVM compilation group measure JIT compilation times as reported by the JVM. | The JVM compilation group measure JIT compilation times as reported by the JVM. | ||
| − | + | ; Compilation Time | |
| + | : the time taken for garbage collection in the last 60 seconds. | ||
== JVM|Memory == | == JVM|Memory == | ||
| Line 45: | Line 46: | ||
The JVM's memory and garbage collection information is useful when tuning memory and checking for memory leak situations, and checking that GC time is in a reasonable range. | The JVM's memory and garbage collection information is useful when tuning memory and checking for memory leak situations, and checking that GC time is in a reasonable range. | ||
| − | + | ; GC Time|PS MarkSweep | |
| − | + | : the GC time taken in the last 60 seconds for full mark-sweep collection as reported by the JVM. | |
| + | ; GC Time|PS Scavenge | ||
| + | : the GC time taken for short GC scavenging as reported by the JVM. | ||
Revision as of 21:58, 19 September 2010
Contents |
Graphs
The Graphs tab in the /resin-admin gives you a view of the meter data collected by Resin across the cluster. The Statistics service that gathers the Meter data is available in Resin Professional.
Graph Browsing
When looking at the server statistics, you first need to select meters to display. Resin's meters are the statistics data streams gathered every minute and stored by the triad servers. Some meters are JMX attributes collected over time, and others record data from Resin's embedded sensors.
Selecting a meter will add the meter to the graph. Once you've selected a group of meters, you can save them as a named meter set using meter save.
Meter Names
Meter names follow a standard convention: "00|Author|Group|Name". The "00" is the server index in the cluster. Author is soemthing like "JVM", "OS", or "Resin", or "MyCom" for custom meters.
Server Groups
Graphs for servers in the cluster can be displayed in three basic modes: single server, one graph, or multiple graphs. In the single graph mode, each meter for each server has its own graph line. In the multiple graph mode, each server gets its own graph. The multiple-graph mode is more useful comparisons across the cluster.
Cookbook: setting up a thread graph
- Clear all the meters by clicking the "Clear Meters" button on the right.
- Open the "JVM|Thread" group to find the recorded data from the JVM's own thread count.
- Select "JVM Thread Count". You should see a graph of the JVM's thread count in the graph. You can use the "Time" selector to change the timescale to use.
- Open the "Resin|Thread" group for the meters in Resin's own thread pool.
- Select all the meters in the "Resin|Thread" group. You should see a graph with about 4 lines visible and the rest at zero.
- Type "threads" in the Meter Save Name form and select "Save Meters". Saving the meters will add "threads" as a predefined meter group in the Meters selection at the top.
Meters
The predefined meters are in three groups: JVM, OS, and Resin.
- JVM is data from the JVM's JMX beans, like thread counts and garbage collection.
- OS is data from the operating system, like CPU counts.
- Resin is data from Resin's JMX and sensors
JVM|Compilation
The JVM compilation group measure JIT compilation times as reported by the JVM.
- Compilation Time
- the time taken for garbage collection in the last 60 seconds.
JVM|Memory
The JVM's memory and garbage collection information is useful when tuning memory and checking for memory leak situations, and checking that GC time is in a reasonable range.
- GC Time|PS MarkSweep
- the GC time taken in the last 60 seconds for full mark-sweep collection as reported by the JVM.
- GC Time|PS Scavenge
- the GC time taken for short GC scavenging as reported by the JVM.
