WAS v8.5 > Tune performance > Tune the application serving environment > Tune operating systems

Tune AIX systems

• TCP_TIMEWAIT

  • Time 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, providing more resources for new connections. Adjust this parameter, if the running application requires rapid release or the creation of new connections, or if a low throughput occurs due to many connections sitting in the TIME_WAIT state.

  • How to view or set:

    Issue the following command to set TCP_TIMEWAIT state to 15 seconds:

    /usr/sbin/no –o tcp_timewait =15

• AIX operating systems with DB2

  • Separating your DB2 log files from the physical database files can boost performance. We can also separate the log and the database files from the drive containing the Journaled File System (JFS) service. AIX uses specific volume groups and file systems for the JFS logging.

  • How to view or set: Use the AIX filemon utility to view all the file system input and output and to strategically select the file system for the DB2 log files. Set the DB2 log location according to the DB2 logging information..

  • Default: The default location for the DB2 log files is often the same disk drive where the database tables are stored.

  • Recommended value: Move the files to a disk that is separate from the DB2 data and has the minimum input or output activity.

• AIX file descriptors (ulimit)

  • Various restrictions on resource usage on the user account. The ulimit -a command displays all the ulimit limits including the number of open files that are permitted. The default number of open files setting (2000) is typically sufficient for most applications. If the value set for this parameter is too low, errors might occur when opening files or establishing connections. Because this value limits the number of file descriptors that a server process might open, a value that is too low prevents optimum performance.

  • How to view or set: Change the open file limit to 10,000 files:
    1. Open the command window.
    2. Edit the /etc/security/limits file. Add the following lines to the user account the WAS process runs on:

       nofiles =  10000 
       nofiles_hard = 10000

    3. Save the changes.

    4. Restart your AIX system.
    5. To verify the result, type the ulimit -a command on the command line.

  • Default: For the AIX operating system, the default setting is 2000.

  • Recommended value: The value is application dependent and applies exclusively to application program data and the application stack.

    Increasing the ulimit file descriptor limits might improve performance. Increasing some of the other limits might be needed depending on the application. Any changes to the data or stack ulimits should ensure that data+stack < 256MB (for 32-bit WAS only).

    It is recommended that you change the ulimit for data to "unlimited".

• AIX TCP_KEEPIDLE

  • How to view or set:

    • If you are on an AIX operating system prior to version 5.2, use the no command to determine the current value or to set the value. The change is effective until the next time you restart the machine. To permanently change the value, add the no command to the /etc/rc.net directory. For example:
      no -o tcp_keepidle=600

    • If you are on an AIX operating system that is version 5.2 and later, use the no -r -o command to determine the value or to set the value. On subsequent reboots, the specified no_optionname value is maintained because it is written to the nextboot file. Set the no command as follows to enable it on future reboots:
      no -r -o arptab_size=10

  • Default: 14400 half seconds (2 hours).

  • Recommended value: 600 half seconds (5 minutes).

• TCP_KEEPINTVL

  • Interval between packets sent to validate the connection.

  • How to view or set: To set the value to 5 seconds:
    no -o tcp_keepintvl=10

  • Default: 150(1/2 seconds)

  • Recommended value: 10(1/2 seconds)

• TCP_KEEPINIT

  • Initial timeout value for TCP connection.

  • How to view or set: To set the value to 20 seconds:
    no -o tcp_keepinit=40

  • Default: 150(1/2 seconds)

  • Recommended value: 40(1/2 seconds)

• Allocating large pages (16 MB) for Java virtual machines heap

  Some applications require a very large heap for optimal performance. Reduce the CPU overhead of managing a large heap using large page support provided by the CPU and the operating system. The following steps allocate 4 GB of RAM as large pages (16 MB):

  1. As root user, run the following commands to reserve 4 GB of large page:

     vmo  -r  -o  lgpg_regions=256  -o lgpg_size=16777216  
     bosboot  -ad  /dev/ipldevice  
     reboot   -q 

  2. After reboot, run the following command to enable large page support on the AIX operating system:
     vmo -p -o v_pinshm=1
  3. As root user, add the following capabilities for the user:
     chuser capabilities=CAP_BYPASS_RAC_VMM,CAP_PROPAGATE $USER

  4. Add the -Xlp Java options to the Java command.

     1. Click Servers > Server Types > WebSphere application servers > server_name.

     2. Under Server Infrastructure, click Java and Process Management > Process definition > Java Virtual Machine.
     3. In the Generic JVM Argument field, add -Xlp.

  5. Add the EXTSHM custom property and set to OFF.

     1. Click Servers > Server Types > WebSphere application servers > server_name.

     2. Under Server Infrastructure, click Java and Process Management > Process definition > Environment Entries > New.
     3. In the Name field, enter EXTSHM.
     4. In the Value field, enter OFF.

  6. Validate large page support is used with the following command:
     vmstat -l 1

     The "alp" column is non-zero when the application is running.

  Enabling large pages might have serious consequences. For more details on large pages, see the information on AIX large pages. If we do not want to use the large pages option, there is also a medium page option. The medium page size option, which is similar, and has close to the same performance gains as large pages. However, it does not involve the problems of reserving physical memory for a specific user or process. For more information, read the Tuning Java virtual machines information.

• Other AIX information

  Consider the other AIX operating system settings that are not within the scope of this document. We can adjust the following additional settings:

  • Adapter transmit and receive queue
  • TCP/IP socket buffer
  • IP protocol mbuf pool performance
  • Update file descriptors
  • Update the scheduler

  For more information about AIX operating systems, see the performance: resources for learning information.

Results

This tuning procedure improves performance of WAS on the AIX operating system.

After tuning your operating system for performance, consult the other tuning topics for various tuning tips.

Related

Tune Windows systems
Tune Linux systems
Tune Solaris systems
Tune HP-UX systems
Tune the IBM virtual machine for Java

Reference:

DB2 tuning parameters
Performance: Resources for learning

Related information:

AIX Large pages

+

Search Tips   |   Advanced Search