This section describes topics on how to tune IBM HTTP Server, including:
- Determining the maximum number of simultaneous connections
- Maximizing client connections to WebSphere Application Server
- Tuning SSL connections
- Network tuning
- Tuning IBM HTTP Server after initial setup
- IBM HTTP Server is configured with some settings out of the box that you might want to change, depending on your needs.
- Determining the maximum number of simultaneous connections
- To ensure the best performance of IBM HTTP Server (IHS), determine the maximum number of connections you require and tune a variety of parameters and directives to take advantage of your needs.
- Maximizing the number of client connections to WebSphere Application Server
- Out of the box, IBM HTTP Server supports a maximum of 600 concurrent connections. Performance will suffer, however, if the load dictates more concurrent connections, as the host operating system will continue to queue incoming requests. You can increase the number of maximum connections that are allowed by IBM HTTP Server by editing the httpd.conf file.
- Avoiding configurations, and recognizing implications of common configurations
- There are some configurations that you should avoid implementing with IBM HTTP Server; these configurations have performance penalties that will impact your environment. In addition, you need to be aware of the implications that some common configurations will have on performance.
- Tuning SSL connections for IBM HTTP Server
- Performance can be improved by tuning how IBM HTTP Server (IHS) handles SSL connections.
- Tuning the network for IBM HTTP Server
- For performance issues that are related to network latency and low transfer rates, you can tune parameters in the operating system or in IBM HTTP Server to improve your performance.
- Memory use comparison between IBM HTTP Server 1.3 and IBM HTTP Server 2.0
-
It has been noted that on AIX, HP-UX, Linux, or Solaris operating systems, there are paging space (swap space) or physical memory problems with IBM HTTP Server 1.3, due to the large number of child processes that might be required and the memory overhead per child process. This comparison illustrates the difference in memory use between IBM HTTP Server 1.3 and IBM HTTP Server 2.0.
- Tuning IBM HTTP Server for AIX, HP-UX, Linux, and Solaris
- There are tuning procedures that you can perform that are specific to AIX, HP-UX, Linux, and Solaris file systems.
- Avoid high CPU usage in child processes after updating WebSphere plugin configuration
- The WebSphere plugin will normally reload the plugin configuration file (plugin-cfg.xml) during steady state operation if the file is modified. When the reload occurs during steady state operation, it must be reloaded in every web server child process that is serving requests. Initialization of https transports is particularly CPU-intensive, so if there are many such transports defined or there are many child processes, the CPU impact can be high.