Performance advisor types and purposes
Two performance advisors are available:
- Performance and Diagnostic Advisor
- Performance advisor in Tivoli Performance Viewer
The Performance and Diagnostic Advisor runs in the JVM process of appserver; therefore, it does not provide expensive advice. In a stand-alone appserver environment, the performance advisor in TPV runs within the appserver JVM.
The performance advisor in TPV provides advice to help tune systems for optimal performance and provide recommendations on inefficient settings by using collected PMI data. Obtain the advice by selecting the performance advisor in TPV.
In a 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 TPV 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 console
- JMX notifications
TPV in the console Frequency of operation Configurable When you select refresh in the TPV 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 diagnostic
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
Sub-topics
Performance and Diagnostic Advisor
Related tasks
Obtaining advice from the advisors