Performance Tuning for Content Manager

Chapter 7. Tuning operating systems for Content Manager 155

7.2.4 Configure disk I/O for effective usage

For an I/O bound system, you can reduce I/O contention by distributing I/O to

multiple disks. We recommend installing the following items to separate physical

disks if the resource is available:

 Library Server database

 Library Server database log

 Resource Manager database

 Resource Manager database log

 Resource Manager LBOSDATA

 Resource Manager staging area

 JFS logs

 Content Manager log file

Consider how your disks are attached to the system. Do not move the bottleneck

from the disk to the disk controller card. Distribute the load over the disk

controller cards.

7.2.5 Set all machines to full duplex

As part of network tuning, always set your machines on the network to the same

value (100 Mbps - full duplex) and be sure that your hub/switch is set to the same

value.

NIC driver settings for auto detection of line speed and direction can sometimes

be misleading. Trouble can sometimes be avoided by explicitly setting the line

speed and direction and not trusting auto-detection settings.

7.2.6 Set MTU size to the maximum supported by LAN

If your traffic is predominantly local, set MTU size to the maximum amount that is

supported by your LAN. This minimizes the fragmentation of packets that are

exchanged by local systems. The offsetting cost is fragmentation in gateways

that connect your LAN to other LANs with smaller MTUs.

On AIX, use the no command to configure network attributes to get the best

result for data transfers. The no command sets or displays current network

attributes in the kernel. This command operates only on the currently running

kernel. The command must be run again after each startup, or after the network