This section discusses miscellaneous Solaris-specific issues and tuning tips, and includes the following topics:
Different platforms have different limits on the number of files that can be open in a single process at one time. For busy sites, increase that number to 8192. To do so on Solaris, make the change in the file /etc/system by setting rlim_fd_max, and then reboot.
Append the following line to the file /etc/system to increase the number of file descriptors for Sun Java System Web Server:
After making this or any change in the /etc/system file, reboot Solaris to put the new settings into effect. In addition, if you upgrade to a new version of Solaris, any line added to /etc/system should be removed and added again only after verifying that it is still valid.
If users are experiencing connection timeouts from a browser to Sun Java System Web Server when the server is heavily loaded, you can increase the size of the HTTP listener backlog queue. To increase this setting, edit the file ListenQ parameter in the magnus.conf file:
In addition to this setting, you must also increase the limits within the Solaris TCP/IP networking code. There are two parameters that are changed by executing the following commands:
/usr/sbin/ndd -set /dev/tcp tcp_conn_req_max_q 8192 /usr/sbin/ndd -set /dev/tcp tcp_conn_req_max_q0 8192
These two settings increase the maximum number of two Solaris listen queues that can fill up with waiting connections. tcp_conn_req_max_q increases the number of completed connections waiting to return from an accept() call. tcp_conn_req_max_q0 increases the maximum number of connections with the handshake incomplete. The default values are 128 and 1024 respectively. To automatically have these ndd commands executed after each system reboot, place them in a file called /etc/init.d/network-tuning and create a link to that file named /etc/rc2.d/S99network-tuning.
You can monitor the effect of these changes by using the netstat -s command and looking at the tcpListenDrop, tcpListenDropQ0, and tcpHalfOpenDrop values. Review them before adjusting these values. If they are not zero, adjust the value to 2048 initially, and continue to monitor the netstat output.
The Sun Java System Web Server ListenQ setting and the related Solaris tcp_conn_req_max_q and tcp_conn_req_max_q0 settings should match the throughput of the Sun Java System Web Server HTTP server. These queues act as a "buffer" to manage the irregular rate of connections coming from web users. These queues allow Solaris to accept the connections and hold them until they are processed by the Sun Java System Web Server HTTP server application.
You do not want to accept more connections than the Sun Java System Web Server HTTP server will be able to process. It is better to limit the size of these queues and reject further connections than to accept excess connections and fail to service them. The value of 2048 for these three parameters will typically reduce connection request failures, and improvement has been seen with values as high as 4096.
This adjustment is not expected to have any adverse impact in any web hosting environment, so you can consider this suggestion even if your system is not showing the symptoms mentioned.
If users are experiencing connection refused errors on a heavily loaded server, you can tune the use of network resources on the server.
When a TCP/IP connection is closed, the port is not reused for the duration of tcp_time_wait_interval (default value of 240000 milliseconds). This is to ensure that there are no leftover segments. The shorter the tcp_time_wait_interval, the faster precious network resources are again available. This parameter is changed by executing the following command (do not reduce it below 60000):
usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000
To automatically have this ndd command executed after each system reboot, place it in a file called /etc/init.d/network-tuning and create a link to that file named /etc/rc2.d/S99network-tuning.
If your system is not exhibiting the symptoms mentioned, and if you are not well-versed in tuning the TCP protocol, it is suggested that you do not change the above parameter.
If you are seeing unpredictable intermittent slowdowns in network response from a consistently loaded server, you might investigate setting the sq_max_size parameter by adding the following line to the /etc/system file:
This setting adjusts the size of the sync queue, which transfers packets from the hardware driver to the TCP/IP protocol driver. Using the value of 512 allows the queue to accommodate high volumes of network traffic without overflowing.
The Solaris Network Cache and Accelerator (SNCA) is a caching server that provides improved web performance to the Solaris operating system. It is available on Solaris 8 Update 5 and higher.
It is assumed that SNCA has been configured for the system on which the Web Server is running. For more information about SNCA and its configuration and tuning, refer to the following man pages on your system:
Enable SNCA to work with Sun Java System Web Server (assuming SNCA configuration, as discussed above)
Edit the Sun Java System Web Server server.xml file so the listen socket on port 80 includes family="nca" as shown below (the server must be listening on port 80 for this to work):
<LS id="ls1" ip="0.0.0.0" port="80" family="nca" security="off" acceptorthreads="1">
Edit the Sun Java System Web Server nsfc.conf file and set the following:
Restart the Web Server for changes to take effect.
When configuring Sun Java System Web Server to be used with SNCA, setting the RqThrottle and ConnQueueSize parameters in magnus.conf to 0 provides better performance. Because SNCA manages the client connections, it is not necessary to set these parameters. These parameters can also be set to 0 with non-SNCA configurations, especially for cases in which short latency responses with no keep-alives must be delivered..
RqThrottle and ConnQueueSize must both be set to 0.
For more information about RqThrottle and ConnQueueSize, see the chapter pertaining to magnus.conf in the Sun Java System Web Server 6.1 SP6 Administrator’s Configuration File Reference. Also consult the RqThrottle and ConnQueueSize entries in the index in this book.