Sun Java System Web Proxy Server 4.0.11 Performance Tuning, Sizing, and Scaling Guide

Using Performance Buckets

Performance buckets enable 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 the data to the bucket. The cost of collecting this information is minimal, and the impact on the server performance is usually negligible. You can access this information by using perfdump. The following information is stored in a bucket:


You must specify all configuration information for performance buckets in the obj.conf file. Only the default-bucket is automatically enabled.

You must enable performance statistics collection and perfdump.

The following examples show how to define new buckets in obj.conf:

Init fn="define-perf-bucket" name="acl-bucket" description="ACL bucket"

The above examples creates a bucket: acl-bucket. To associate this bucket with functions, add bucket=bucket-name to the obj.conf function for which to measure performance.


PathCheck fn="check-acl" acl="default" bucket="acl-bucket"
Service method="(GET|HEAD|POST)" type="*~magnus-internal/*" 
fn="send-file" bucket="file-bucket"
<Object name="cgi">
ObjectType fn="force-type" type="magnus-internal/cgi"
Service fn="send-cgi" bucket="cgi-bucket"

Performance Report

The Server statistics in buckets can be accessed by using perfdump. The performance buckets information is located in the last section of the report returned by perfdump.

The report contains the following information:

The following example shows performance bucket information in perfdump:

Performance Counters:
                           Average         Total      Percent

Total number of requests:               62647125
Request processing time:    0.0343  2147687.2500

default-bucket (Default bucket)
Number of Requests:                     62647125    (100.00%)
Number of Invocations:                3374170785    (100.00%)
Latency:                    0.0008    47998.2500    (  2.23%)
Function Processing Time:   0.0335  2099689.0000    ( 97.77%)
Total Response Time:        0.0343  2147687.2500    (100.00%)