Performance Tuning for Content Manager

256 Performance Tuning for Content Manager

9.1 Introduction

Tuning WebSphere for Content Manager is about processing as many requests

as possible by utilizing the resources to their fullest potential. Many components

in WebSphere Application Server have direct performance impact on Resource

Manager. This chapter covers the tuning area including our recommendations

that might have implications on Resource Manager performance.

As a shortcut into WebSphere tuning, we offer Table 9-1. This table is designed

for easy access to symptoms and related tuning area for the symptoms.

Table 9-1 WebSphere performance tuning short cut

Much of the material provided here is extracted from IBM WebSphere Application

Server, Version 5.1: Monitoring and Troubleshooting, found in:

http://www.ibm.com/software/webservers/appserv/was/library

For more in-depth tuning information, you can also check out the WebSphere

Application Server Information Center:

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1/index.jsp

Symptoms Related tuning area

Throughput and response time are

undesirable.

Processor speed

AIX: Memory allocation error. AIX file descriptors (ulimit)

Windows NT or 2000: Netstat shows too

many sockets are in TIME_WAIT.

Windows NT or 2000 TcpTimedWaitDelay

Throughput is undesirable and the

application server priority has not been

adjusted.

Adjusting the operating system priority of

the WebSphere Application Server

process

Under load, client requests do not arrive at

the Web server because they time out or

are rejected.

For IBM HTTP Server on Windows NT,

see ListenBackLog

Tivoli Performance Viewer Percent Maxed

Metric indicates that the Web container

thread pool is too small.

Thread pool

Netstat shows too many TIME_WAIT state

sockets for port 9080.

MaxKeepAliveConnections,

MaxKeepAliveRequests

Too much disk input/output occurs

due to paging.

Heap size settings