Monitoring Server Performance

Makingthe adjustments described in this guide without measuring their eects doesn’t make

sense.If you don’t measure the system’sbehavior before and after making a change, you won’t

knowwhether the change was a good idea, a bad idea, or merely irrelevant. You can monitor the

performanceof Web Server in several dierent ways.

TABLE1–1 Methodsof MonitoringPerformance
MonitoringMethod HowtoEnable HowtoAccess AdvantagesandRequirements
Statisticsthrough the
AdminConsole
Enabledby default Inthe Admin Console, for a
conguration,click the
Monitortab
Accessiblewhen session
threadsare hanging.
AdministrationServer
mustbe running.
Statisticsthrough
individualwadm
commands
Enabledby default Throughwadm commands:
get-config-stats
get-virtual-server-stats
get-webapp-stats
get-servlet-stats
Accessiblewhen session
threadsare hanging.
AdministrationServer
mustbe running.
XML-formattedstatistics
(stats-xml)through a
browser
Enablethrough
AdminConsole or
throughediting a
congurationle
Througha URI AdministrationServer
neednot be running.
XML-formattedstatistics
(stats-xml)through the
command-lineinterface
Enabledby default Throughthe wadm command
get-stats-xml
Accessiblewhen session
threadsare hanging.
AdministrationServer
mustbe running.
perfdumpthrough a
browser
Enablethrough
AdminConsole or
throughediting a
congurationle
Througha URI AdministrationServer
neednot be running.
perfdumpthrough the
command-lineinterface
Enabledby default Throughwadm command
get-perfdump
Accessiblewhen session
threadsare hanging.
AdministrationServer
mustbe running.
JavaES Monitoring Enabledby default Throughthe Java ES
MonitoringConsole
Onlyfor Java ES
installations.
AdministrationServer
mustbe running.

Monitoringthe server does have some impact on computing resources. In general, using

perfdumpthrough the URI is the least costly, followed by using stats-xml through a URI.

MonitoringServer Performance
SunJavaSystem Web Server 7.0 Update 1 Performance Tuning,Sizing, and Scaling Guide •22