Sun Microsystems Sun Java System Web Server 7.0, Manual

Page: 35 / 132

29133 response 192.6.7.7 2 https-test GET /qa_webapp/CheckNetwork.class service-j2ee
29133 response 192.6.7.7 2 https-test GET /qa_webapp/CheckNetwork.class service-j2ee
29133 response 192.6.7.7 2 https-test GET /qa_webapp/CheckNetwork.class service-j2ee
29133 response 192.6.7.7 2 https-test GET /qa_webapp/CheckNetwork.class service-j2ee
29133 request 192.6.7.7 0
29133 request 192.6.7.7 0
29133 request 192.6.7.7 0
29133 request 192.6.7.7 0
29133 request 192.6.7.7 0
29133 response 192.6.7.7 0 https-test GET /file1.shtml shtml_send
29133 request 192.6.7.7 0
29133 request 192.6.7.7 0
29133 response 192.6.7.7 0 https-test GET /find-pathinfo-forward/pathinfo.pl/p/info send-cgi
29133 request 192.6.7.7 0
29133 updating 192.6.7.7
29133 updating 192.6.7.7
29133 updating 192.6.7.7
29133 updating 192.6.7.7
.
.
.
Using Performance Buckets
Performance buckets allow you to define buckets and link them to various server functions.
Every time one of these functions is invoked, the server collects statistical data and adds it to the
bucket. For example,
send-cgi
and
service-j2ee
are functions used to serve the CGI and Java
servlet requests respectively. You can either define two buckets to maintain separate counters
for CGI and servlet requests, or create one bucket that counts requests for both types of
dynamic content. The cost of collecting this information is minimal, and the impact on the
server performance is usually negligible. This information can later be accessed using
perfdump
.
The following information is stored in a bucket:
■
Name of the bucket. This name associates the bucket with a function.
■
Description. A description of the functions with which the bucket is associated.
■
Number of requests for this function. The total number of requests that caused this
function to be called.
■
Number of times the function was invoked. This number might not coincide with the
number of requests for the function, because some functions might be executed more than
once for a single request.
■
Function latency or the dispatch time. The time taken by the server to invoke the function.
■
Function time. The time spent in the function itself.
The
default-bucket
is predefined by the server. It records statistics for the functions not
associated with any user-defined bucket.
Monitoring Server Performance
Chapter 1 • Performance and Monitoring Overview 35