Monitoring Server Performance

                                                                                                                                                                                                                                                                                                                                      Back to [Book]     [Topic]

Monitoring Server Performance

Making the adjustments described in this guide without measuring their effects does not make sense. If you do not measure the system’s behavior before and after making a change, you would not know whether the change was a good idea, a bad idea, or merely irrelevant. You can monitor the performance of Web Server in several different ways.

Table 1-1 Methods of Monitoring Performance

Monitoring Method How to Enable How to Access Advantages and Requirements
Statistics through the Admin Console Enabled by default In the Admin Console, for a configuration, click the Monitor tab Accessible when session threads are hanging. Administration Server must be running.
Statistics through individual wadm commands Enabled by default Through wadm commands:
get-config-stats
get-virtual-server-stats
get-webapp-stats
get-servlet-stats
Accessible when session threads are hanging. Administration Server must be running.
XML-formatted statistics (stats-xml) through a browser Enable through Admin Console or through editing a configuration file Through a URI Administration Server need not be running.
XML-formatted statistics (stats-xml) through the command-line interface Enabled by default Through the wadm command
get-stats-xml
Accessible when session threads are hanging. Administration Server must be running.
perfdump through a browser Enable through Admin Console or through editing a configuration file Through a URI Administration Server need not be running.
perfdump through the command-line interface Enabled by default Through wadm command
get-perfdump
Accessible when session threads are hanging. Administration Server must be running.
Java ES Monitoring Enabled by default Through the Java ES Monitoring Console Only for Java ES installations. Administration Server must be running.

Monitoring the server does have some impact on computing resources. In general, using perfdump through the URI is the least costly, followed by using stats-xml through a URI. Because using the Administration Server requires computing resources, the command-line interface and the Admin Console are the most costly monitoring methods.

For more information on these monitoring methods, see the following sections:

Labels

web web Delete
scaling scaling Delete
+tuningguide +tuningguide Delete
tuning tuning Delete
java java Delete
server server Delete
sun sun Delete
webserver webserver Delete
application application Delete
system system Delete
performance performance Delete
webserver70 webserver70 Delete
sunjava sunjava Delete
sizing sizing Delete
other other Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact