Chapter 5. Operating system considerations 335
If too many are configured, the threads will not be used; if too few are
configured, performance degrades. While there are several rules of thumb for
determining the correct numbers, we recommend the following:
–Set maxAIOservers to the maximum of:
• Minimum of 10 times the number of database disks, or 10 times the
number of CPUs in the system
• At least one per page cleaner and prefetcher (per instance)
– A good value for minAIOservers is maxAIOservers/2.
The following command displays the current settings of these variables:
lsattr -El aio0
DB2-specific recommendations
We recommend the following DB2-specific best practices:
1. DB2 in 64-bit mode enables DB2 to use larger heaps, but the DB2 processes
such as db2agent also use more memory. This additional memory
(approximately 50 KBytes per process) needs to be factored into memory
usage computations. However, in most situations, heap usage outweighs
process memory usage and the overhead of 64-bit process memory usage is
not a consideration.
2. If you run a DB2 32-bit application on a 64-bit database, you will need to
rebind the application and set UNIX environment variables to point to the
32-bit libraries, for example:
LIBPATH=<db2instance home>/sqllib/lib32
export LIBPATH
3. Multiple versions of DB2 ESE can be installed on the same system. With DB2
V8.1 Fixpak 2, multiple fixpaks of the same DB2 version can also coexist on
the same system.
5.2.2 Memory considerations
In this section, we provide the following:
1. A review of the AIX virtual memory architecture
2. General performance recommendations
3. DB2-specific recommendations
AIX virtual memory architecture review
Virtual memory provides a mechanism for the system to assign more memory to
processes than physically exists on the system. It does this by moving (or