Performance advisor types and purposes
Two performance advisors are available:
Performance and Diagnostic Advisor Runs in the JVM process of appserver; therefore, it does not provide expensive advice. Performance advisor in Tivoli Performance Viewer Uses collected PMI data In an ND environment, the performance advisor in TPV runs within the JVM of the node agent and can provide advice on resources that are more expensive to monitor and analyze. The TPV advisor requires that you enable performance modules, counters, or both.
The following chart shows the differences between the Performance and Diagnostic Advisor and the Tivoli Performance Viewer advisor:
Performance and Diagnostic Advisor Tivoli Performance Viewer advisor Start location Application Server TPV client Invocation of tool Administrative console TPV Output
- The SystemOut.log file
- The admin console
- JMX notifications
TPV in the admin console Frequency of operation Configurable When you select refresh in the TPV admin console Types of advice Performance advice:
- (ORB) service thread pools
- Web container thread pools
- Connection pool size
- Persisted session size and time
- Prepared statement cache size
- Session cache size
- Memory leak detection
Diagnostic advice:
- Connection factory diagnostics
- Data source diagnostics
Connection usage diagnostics
- Detection of connection use by multiple threads
- Detection of connection use across components
Performance advice:
- ORB service thread pools
- Web container thread pools
- Connection pool size
- Persisted session size and time
- Prepared statement cache size
- Session cache size
- Dynamic cache size
- JVM heap size
- DB2 Performance Configuration wizard
Subtopics
Performance and Diagnostic Advisor
Related tasks
Obtaining advice from the advisors