Runtime Performance Advisor uses Performance Monitoring
Infrastructure (PMI) data to provide recommendations for performance
tuning.
About this task
The
Performance and Diagnostic Advisor uses
Performance Monitoring Infrastructure (PMI) data to provide recommendations
for performance tuning. Running in the Java virtual
machine (JVM) of the application server, this advisor periodically
checks for inefficient settings, and issues recommendations as standard
product warning messages.
Procedure
The Performance and Diagnostic Advisor recommendations
are displayed in two locations:- The WebSphere® Application Server SystemOut.log log
file.
- The Runtime Messages panel in the
administrative console.
To view this administrative page, click Troubleshooting > Runtime
Messages > Runtime Warning.
Example
The following log file is a sample
output of advice on the
SystemOut.log file:
[4/2/04 15:50:26:406 EST] 6a83e321 TraceResponse W CWTUN0202W:
Increasing the web container thread pool Maximum Size to 48
might improve performance.
Additional explanatory data follows.
Average number of threads: 48.
Configured maximum pool size: 2.
This alert has been issued 1 time(s) in a row.
The threshold will be updated to reduce the
overhead of the analysis.
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.