Performance Tuning for Content Manager

Chapter 9. Tuning WebSphere for Content Manager 269

Manager System such as DB2. Make small increment changes at a time. If the

trade-off is not acceptable, then go back to the previous value. By improving the

priority of an application server, noticeable improvements have been seen on

AIX; but you always want to be able to balance performance of all components of

Content Manager and avoid bottlenecks.

9.5.2 Web container maximum thread size

To route servlet requests from the Web server to the Web containers, the product

establishes a transport queue between the Web server plug-in and each Web

container. Use this configuration to specify the maximum number of threads that

can be pooled to handle requests sent to the Web container. Requests are sent

to the Web container through any of the HTTP transports.

Default values

50

How to view or set

1. In the administrative console, select the application server you are tuning.

2. Under Additional Properties, click Web Container.

3. Under Additional Properties, click Thread Pool.

4. Enter the desired maximum number of maximum threads in the Maximum

Size field.

5. Select the Growable Thread Pool (see below) check box.

6. Click Apply or OK.

7. Click Save.

Our recommendation

Tivoli Performance Viewer displays a metric called Percent Maxed that

determines the amount of time that the configured threads are in use. If this value

is consistently in the double digits, the Web container could be a bottleneck and

the number of threads should be increased.

9.5.3 Thread allocation beyond maximum

When this option is selected (enabled), more Web container threads can be

allocated than specified in the maximum thread size field. When unselected, the

thread pool cannot grow beyond the value specified for the maximum thread size.

Default values

Unchecked