WAS v8.5 > Tune performance > Obtain advice from the advisors > Why to use the performance advisorsPerformance advisor types and purposes
Two performance advisors are available:
- 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.
- Performance advisor in Tivoli Performance Viewer
Provides advice to help tune systems for optimal performance and provide recommendations on inefficient settings
Obtain the advice by selecting the performance advisor in Tivoli Performance Viewer.
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 dmgr console
- JMX notifications
Tivoli Performance Viewer in the dmgr console Frequency of operation Configurable Select refresh in the Tivoli Performance Viewer dmgr console Types of advice Performance advice:
- ORB
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 HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.
Subtopics
- Performance and Diagnostic Advisor
- Obtain advice from the advisors
Troubleshoot applications with HPEL