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 Java™ virtual machine (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 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 you enable performance modules, counters,
or both.
Table 1. 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 administrative console
- JMX notifications
|
Tivoli Performance Viewer in
the administrative console |
Frequency of operation |
Configurable |
When you select refresh in the Tivoli Performance
Viewer administrative console |
Types of advice |
Performance advice:
- Object Request Broker (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
- Java virtual machine (JVM) heap size
- DB2® Performance Configuration wizard
|
Note: Cette rubrique fait référence à un ou plusieurs des fichiers journaux de serveur d'applications. Il est recommandé de configurer le serveur de telle sorte qu'il utilise l'infrastructure de journalisation et de trace HPEL (High Performance Extensible Logging) à la place des fichiers SystemOut.log, SystemErr.log, trace.log et activity.log sur les systèmes distribués et IBM® i. Vous pouvez également utiliser HPEL conjointement avec vos fonctions de journalisation z/OS® natives. Si vous utilisez l'infrastructure HPEL, vous pouvez accéder à toutes les informations de journalisation et de trace en utilisant l'outil de ligne de commande LogViewer à partir de votre répertoire bin de profil de serveur. Pour plus d'informations sur l'utilisation de HPEL, voir les informations sur l'utilisation de HPEL
en vue du traitement des incidents liés aux applications.