Operating System Configuration

4. Operating System Configuration

Tuning can be applied at the operating system (OS) level on servers and clients to optimize performance of TRIRIGA®.

4.1 Server Operating System Configuration

Tuning can be applied at the operating system (OS) level on servers to optimize performance of TRIRIGA. While these settings are recommended for optimal performance, you should consult with your systems and network administrators before using these settings to ensure they are compatible with any standards in place for your organization.

4.1.1 Red Hat Linux Configuration

Default settings for TCP and UDP tunables on Linux® are good and recommended by TRIRIGA. However, a few settings should be modified for best performance.

For networking, use the following settings:

sysctl -w net.ipv4.ip_local_port_range="1024 65535"

For resources (ulimit values), use the following settings:

max user processes (-u) 8192 
open files         (-n) 131072

For shared memory on DB2 servers, see Modifying kernel parameters (Linux).

For shared memory on Oracle servers, see Configuring Kernel Parameters and Resource Limits.

4.1.2 Windows Configuration

Set the following networking parameters, located under the Windows registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

TcpTimedWaitDelay         dword:0000001e (30)
StrictTimeWaitSeqCheck    dword:00000001 (1)
MaxFreeTcbs               dword:00011940 (72000)
MaxHashTableSize          dword:0000ffff (65535) T
cpWindowSize              dword:0000ffff (65535)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces

TcpAckFrequency           dword:00000001 (1)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AFD\Parameters

EnableDynamicBacklog      dword:00000001 (1)
MinimumDynamicBacklog     dword:00000032 (50)
MaximumDynamicBacklog     dword:000003e8 (1000)
DynamicBacklogGrowthDelta dword:0000000a (10)

If some of the above parameters are not in the registry, they may be added as follows at Add a Value to a Registry Key Entry.

For Windows Server, the default start port is 49152 and the default end port is 65535. Therefore, 16384 ports are available by default.

To view the dynamic port range, start the Command Prompt and use the netsh command, as follows:

netsh int ipv4 show dynamicport tcp

To change the dynamic port range for the maximum number of ports allowed, issue the following command:

netsh int ipv4 set dynamicport tcp start=1025 num=64510

Note that the minimum start port is 1025 and the maximum end port cannot exceed 65535.

4.2 Client Operating System Configuration

Tuning can be applied at the operating system (OS) level on clients to optimize performance of TRIRIGA. Customers report that client workstation configuration is, initially, the most important area to focus on when users experience performance issues.

Hardware and software products constantly evolve. TRIRIGA can run on some older hardware and software platforms. The best performance is achieved by using the newest supported operating systems and the latest hardware. Robust workstations provide better performance. For example, client workstations must have, at least, the minimum RAM required by the operating system and by all other applications that it runs, but adding more RAM can boost performance. Similarly, using workstations with multiple CPUs and higher clock speeds also boosts performance.

  • Limit or prevent some workstation activities and processes. Customers report that some user activities and workstation processes can degrade performance. Check for and monitor these activities and processes, and respond as necessary.
  • Monitor the network for streaming audio and video. Customers report that monitoring the network to prevent users from using streaming audio and video can noticeably increase the bandwidth available to the system.
  • Have only one network link active. If a user has both a wireless network link and an active LAN link, it can cause system performance issues. Limit users to one active network link.
  • Monitor for hanging processes and applications. Processes and applications that are not responding (are hanging) use memory and can affect the performance of the client workstation. A workstation can have hanging processes or applications of which the user might not be aware. Use system tools, such as the Windows Task Manager, to check for and end hanging processes and applications.

For more information on supported (desktop) client workstations, see the IBM TRIRIGA Compatibility Matrix.