Network Deployment (Distributed operating systems), v8.0 > Tune performance > Obtaining advice from the advisors > Why to use the performance advisors
Performance advisor types and purposes
Two performance advisors are available: the Performance and Diagnostic Advisor and the performance advisor in Tivoli Performance Viewer.
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 by using collected Performance Monitoring Infrastructure (PMI) data. Obtain the advice by selecting the performance advisor in Tivoli Performance Viewer.
In a WAS ND 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 you enable performance modules, counters, or both.
Performance and Diagnostic Advisor and Tivoli Performance Viewer advisor. 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 Tivoli Performance Viewer client Invocation of tool Administrative console Tivoli Performance Viewer Output
- The SystemOut.log file
- The admin console
- JMX notifications
Tivoli Performance Viewer in the admin console Frequency of operation Configurable When you select refresh in the Tivoli Performance Viewer 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
With WAS v8 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using $PROFILE/bin/LogViewer.sh.
Related
Performance and Diagnostic Advisor
Obtaining advice from the advisors
Use HPEL to troubleshoot applications