Performance advisor types and purposes
Two performance advisors are available:
The Performance and Diagnostic Advisor runs in the JVM process of application server; therefore, it does not provide expensive advice. In a stand-alone application server environment, the performance advisor in Tivoli Performance Viewer runs within the application server JVM.
The performance advisor in Tivoli Performance Viewer provides advice to help tune systems for optimal performance and provide recommendations on inefficient settings using collected Performance Monitoring Infrastructure (PMI) data. Obtain the advice by selecting the performance advisor in Tivoli Performance Viewer.
In a WebSphere Application Server, Network Deployment environment, the performance advisor in Tivoli Performance Viewer runs within the JVM of the node agent and can provide advice on resources that are more expensive to monitor and analyze. The Tivoli Performance Viewer advisor requires that we enable performance modules, counters, or both.
Performance and Diagnostic Advisor Tivoli Performance Viewer advisor Start location Application server Tivoli Performance Viewer client Invocation of tool Administrative console Tivoli Performance Viewer Output
- The SystemOut.log file
- The administrative console
- JMX notifications
Tivoli Performance Viewer in the administrative console Frequency of operation Configurable When we select refresh in the Tivoli Performance Viewer administrative 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
IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure. We view HPEL log and trace information using the logViewer .
Subtopics
Obtain advice from the advisors Use High Performance Extensible Logging to troubleshoot applications