Service Tuning

The Service Tuning page allows you to set or adjust properties that affect service performance. There are three categories of performance tuning:

For more information on performance tuning, see Tuning the Java Web Server.

These settings affect the general performance of the service:

Capacity - Sets the maximum number of concurrent client connections that the service allows. The default is 50 connections.
Memory Cache Entry - Sets the size of each entry in the server's memory cache. Setting the cache size to zero disables it. The default is between 1-8 MB.

These settings affect the performance of threads within the service.

Minimum - Sets the minimum number of threads the service maintains in its handler pool to service incoming requests. Because thread creation adds overhead to the service's response time, it's recommended that you set this property to a non-zero value. The default is 10 threads.
Maximum - Sets the maximum number of threads the service maintains in its handler pool to service incoming requests. The default is 50 threads.
Timeout - Sets the expiration timeout for an idle handler thread. The default is 300 seconds.

These settings affect the way the service handles TCP/IP connections.

Keep Alive - Sets the number of HTTP requests to allow on a single TCP/IP connection before terminating the connection. The default is 5 requests.
Timeout - Sets the number of seconds before dropping an idle connection. The default is 30 seconds.

To make changes to the Service Tuning page and have those settings take affect, use the three buttons at the bottom of the screen. These are:

Save - Writes your changes to the Java Web Server and changes the settings.
Revert - Takes you back to the previous settings for all fields in the screen. Use this button to undo changes you have not yet saved.
Defaults - Displays the settings that were active when you entered the Java Web Server Service Tuning page.