Performance Tuning for Content Manager

166 Performance Tuning for Content Manager

7.4.7 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

 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.4.8 Set the /3GB parameter option in boot.ini

By default, the 32-bit editions of Windows can address a total of 4 GB of virtual

address space. This is the limitation of the 32-bit architecture. Normally, 2 GB of

this is reserved for the operating system kernel requirements (privileged-mode)

and the other 2 GB is reserved for application (user-mode) requirements. Under

normal circumstances, this creates a 2 GB per-process address limitation. For

Content Manager, the user-mode process affected is db2syscs.exe, and for

Oracle, the affected process is oracle.exe.

Windows provides a /3GB parameter to be added to the boot.ini file that

reallocates 3 GB of memory to be available for user-mode applications and

reduces the amount of memory for the system kernel to 1 GB. Both DB2 and

Oracle can derive performance benefits from having large amounts of

addressable memory available for creating agent processes that handle a large

number of concurrent database connections.

To edit the boot.ini file to make this change, complete the following steps:

1. Open the System Control Panel.

2. Select the Advanced tab.

3. In the Startup and Recovery frame, click Settings.

4. Click Edit. Notepad opens to edit the current boot.ini file.

5. Edit the current ARC path to include the /3GB switch in the same line that has

/fastdetect.

6. Restart the server for the change to take effect.