Sun Java System Web Server 6.1 SP9 Performance Tuning, Sizing, and Scaling Guide

Activating Statistics

You must activate statistics on Sun Java System Web Server before you can monitor performance. This can be done through the Server Manager, or by editing the obj.conf and magnus.conf files.

Caution – Caution –

When you activate statistics/profiling, statistics information is made available to any user of your server.

Activating Statistics from the Server Manager

You can activate statistics from the user interface.

ProcedureTo activate statistics from the user interface

  1. From the Server Manager, click the Monitor tab, and then click Monitor Current Activity.

    The Enable Statistics/profiling page appears.

  2. Select Yes to activate Statistics/Profiling.

  3. Click OK, click Apply, and then click the Apply Changes button to activate Statistics/Profiling.

Activating Statistics with stats-xml

You can also activate statistics directly by editing the obj.conf and magnus.conf files. Users who create automated tools or write customized programs for monitoring and tuning may prefer to work directly with stats-xml.

ProcedureTo activate statistics using stats-xml

  1. Under the default object in obj.conf, add the following line:

    NameTrans fn="assign-name" from="/stats-xml/*" name="stats-xml"

  2. Add the following Service function to obj.conf:

    <Object name="stats-xml"> Service fn="stats-xml" </Object>

  3. Add the stats-init SAF to magnus.conf.

    Here's an example of stats-init in magnus.conf:

    Init fn="stats-init" update-interval="5" virtual-servers="2000" profiling="yes"

    The above example shows you can also designate the following:

    • update-interval. The period in seconds between statistics updates. A higher setting (less frequent) will be better for performance. The minimum value is 1; the default value is 5.

    • virtual-servers. The maximum number of virtual servers for which you track statistics. This number should be set equal to or higher than the number of virtual servers configured. Smaller numbers result in lower memory usage. The minimum value is 1; the default is 1000.

    • profiling. Activate NSAPI performance profiling. The default is "no," which results in slightly better server performance. However, if you activate statistics through the user interface, profiling is turned on by default.