The following tuning parameters are specific to the Solaris operating
system. Because the Solaris operating system is not a WebSphere Application
Server product, be aware that it can change and results vary.
About this task
On the Solaris operating system, WebSphere Application Server runs
on the Sun Hotspot Java virtual machine (JVM). It is important to use the
correct tuning parameters with the Sun JVM to utilize its performance optimizing
features. Refer to the
Tuning Java virtual machines topic for more information about tuning the JVM.
Also, consider the following parameters that are specific to the Solaris
operating system to ensure that WebSphere Application Server has enough resources.
Procedure
Configure the following settings or variables according to your
tuning needs:
- Solaris file descriptors (ulimit)
- Description: Specifies the maximum number of open files supported.
If the value of this parameter is too low, a Too many files open error
is displayed in the WebSphere Application Server stderr.log file.
- How to view or set: Check the UNIX reference pages on the ulimit command
for the syntax of different shells. For the KornShell (ksh) shell use the ulimit
-n 1024 command. Use the ulimit -a command to display the current
settings. Use the ulimit -n 2000 command to set the values.
- Default value: None
- Recommended value: 8000
- Solaris TCP_TIME_WAIT_INTERVAL
- Solaris TCP_FIN_WAIT_2_FLUSH_INTERVAL
- Solaris TCP_KEEPALIVE_INTERVAL
- Solaris kernel semsys:seminfo_semopm
- Description: An entry in the /etc/system file
can exist for this tuning parameter. This number is the maximum value of System
V semaphore operations per semop call. The default value for this option is
too low for highly concurrent systems.
- How to view or set: Set this parameter through the /etc/system entry: semsys:seminfo_semopm
= 200
- Default value: None
- Recommended value: 200 (100 is appropriate for most systems, but
200 might be needed in some cases.)
Note: This parameter has been superseded on the Solaris
10 operating system by the process.max-sem-ops resource control, which now
has a default value of 512 per process. This default is sufficient for most
applications. For more information on Solaris 10 parameters and resource controls,
search for "tunable parameters" and "resource control" on the Sun Microsystems
Web site at: http://docs.sun.com.
- Connection backlog
- Large page support
Using large pages can reduce
the CPU overhead of managing a large JVM heap. .
With Solaris 9 and
Solaris 10, large page support is provided by default. No operating system
or JVM parameters are necessary to make use of large pages for the JVM heap
Results
This tuning procedure improves the performance of WebSphere Application
Server on the Solaris operating system.
What to do next
After tuning your operating system for performance, consult other
tuning topics for various tuning tips.