Performance Tuning for Content Manager

164 Performance Tuning for Content Manager

Our recommendation

Content Manager usually creates files with the first six characters that are the

same. By disabling the 8.3 file name creation, you avoid the NTFS overhead of

creating the short name files for Content Manager long-name (30 CHARS) files

that it stored in the LBOSDATA area. From our experience, this improves system

performance.

7.4.5 Check memory

Verify that you have enough physical memory for your Content Manager system.

For a Library Server machine, you should have about 1 GB RAM plus 10 MB

RAM for each Windows desktop client plus about 10 MB RAM for every 20 Web

clients without DB2 Connection concentrator turned on. With DB2 Version 8.1

Connection concentrator turned on, allocate about 10 MB RAM for every 10

desktop clients.

7.4.6 Tune Windows network

For Windows servers, use both the network adapter properties and Windows

registry to update the TCP layer parameters. Table 7-2 lists the registry entries,

parameters, and recommended values. If your environment is uniformly Windows

platform, make sure all of these parameters are set to the same values across all

of your servers (that is, the Library Server, Resource Manager server, and

eClient Server) to optimal network throughput. We recommend that you restart

your server for these changes to take effect.

Table 7-2 Windows 2003 TCP tuning for CM

Registry entry Parameter and value

HKEY_LOCAL_MACHINE\SYSTEM\Curre

ntControlSet\Services\T

CPIP\Parameters

TcpTimedWaitDelay= 30 (decimal)

MaxUserPort= 32768 (dec)

KeepAliveInterval= 1 (dec)

HKEY_LOCAL_MACHINE\SYSTEM\Curre

ntControlSet\Services\T

cpip\Parameters\Interfaces\

TcpAckFrequency= 1

Tcpip\Parameters\Interfaces\ID TcpMaxDataretranmissions= 5 (dec)

Chapter 7. Tuning operating systems for Content Manager 165

The descriptions of the tuned TCP parameters are as follows:

 TcpTimedWaitDelay: Determines the time (in seconds) that must elapse

before TCP/IP can release a closed connection and reuse its resources. This

interval between closure and release is known as the TIME_WAIT state or

twice the maximum segment lifetime (2MSL) state. During this time,

reopening the connection to the client and server costs less than establishing

a new connection. By reducing the value of this entry, TCP/IP can release

closed connections faster and provide more resources for new connections.

Adjust this parameter if your Content Manager application requires rapid

release, the creation of the new connections, or an adjustment because of a

low throughput caused by multiple connections in the TIME_WAIT state.

 MaxUserPort: Determines the highest port number that TCP/IP can assign

when an application requests an available user port from the system.

 KeepAliveInterval: Determines how often TCP repeats keep-alive

transmissions when no response is received.

 TcpAckFrequency: TCP/IP can be the source of some significant remote

method delays. You can increase TCP performance by immediately

acknowledging incoming TCP segments, in all situations.

 TcpMaxDataRetransmissions: Determines how many times TCP retransmits

an unacknowledged data segment on an existing connection.

 MaxConnect Backlog: If many connection attempts are received

simultaneously, increase the default number of pending connections that are

supported by the operating system. Set all four parameters according to the

table above, Enable DynamicBacklog, MinimumDynamicBacklog,

MaximumDynamicBacklog, and DynamicBacklogGrowthDelta.

For more information about the network driver, refer to:

http://www.microsoft.com/whdc/device/network/taskoffload.mspx#EEAA

HKEY_LOCAL_MACHINE\SYSTEM\Curre

ntControlSet\Services\A

FD\Parameters

"EnableDynamicBacklog"=dword:000000

01

"MinimumDynamicBacklog"=dword:00000

020

"MaximumDynamicBacklog"=dword:00001

000

"DynamicBacklogGrowthDelta"=dword:0

0000010

Registry entry Parameter and value