This topic describes how to tune the Linux® operating system to optimize the performance of your WebSphere® Application Server.
About this task
When you have a performance concern, check the operating system settings to determine if
these settings are appropriate for your application. Because the Linux operating system is not a WebSphere Application Server product, be aware that it can change and results can
vary.
Procedure
Configure the following settings and variables according to your tuning needs:
- Changing TCP parameters
- Linux file
descriptors (ulimit)
- Description: Specifies the number of open files that are supported. The default setting
is typically sufficient for most applications. If the value set for this parameter is too low, a
file open error, memory allocation failure, or connection establishment error might be
displayed.
- How to view or set: Check the UNIX reference pages on the ulimit command for the syntax of different
shells. To set the ulimit command to 8000 for the KornShell shell (ksh), issue the
ulimit -n 8000 command. Use the ulimit -a command to display the current values for
all limitations on system resources.
- Default value: For SUSE Linux Enterprise Server 9 (SLES 9), the default is 1024.
- Recommended value:
8000
- Connection backlog
- Firewalls typically have a connection expiration timeout: if there is
no activity on a connection within the timeout interval, the connection
is removed from the firewall routing tables. If connections between
servers, such as a connection pool between a server and a backend
database, are timed out by a firewall between the systems, attempts to
reuse the connection fail until the connection is reestablished,
causing errors and performance issues. To avoid this type of problem,
you can configure the TCP keepalive function to operate on an interval
that is shorter than the firewall timeout. The TCP keepalive activity
informs the firewall that the connection is still in use, so the
connection does not expire and be flushed from the firewall tables.
To perform this tuning, first determine the firewall connection
expiration timeout. The network administrator typically knows this
information. Next, set the following three TCP tuning options to
run TCP keepalive at an interval comfortably shorter than connection
expiration timeout. Thus, for a firewall connection expiration timeout
of 75 seconds, set the TCP tuning options to run TCP keepalive at an
interval less than 75 seconds. Add the options to the
/etc/sysctl.conf file to survive restarts.
- TCP_KEEPALIVE_TIME
- TCP_KEEPALIVE_INTERVAL
- TCP_KEEPALIVE_PROBES
Results
This tuning procedure improves performance of WebSphere Application Server on the Linux operating system.
What to do next
After tuning your operating system for performance, consult other tuning topics for various
tuning tips.