Tuning Solaris for Performance Benchmarking
Tuning Solaris for Performance Benchmarking
The following table shows the operating system tuning for Solaris used when benchmarking for
performance and scalability. These values are an example of how you might tune your system to
achieve the desired result.
TABLE 4–1
Parameter
rlim_fd_max
sq_max_size
tcp_time_wait_interval
tcp_conn_req_max_q
tcp_conn_req_max_q0
tcp_ip_abort_interval
tcp_keepalive_interval
tcp_rexmit_interval_initial
tcp_rexmit_interval_max
tcp_rexmit_interval_min
tcp_smallest_anon_port
tcp_slow_start_initial
tcp_xmit_hiwat
tcp_recv_hiwat
96
Sun Java System Web Server 7.0 Update 1 Performance Tuning, Sizing, and Scaling Guide •
Tuning Solaris for Performance Benchmarking
Scope
Default Value
65536
/etc/system
2
/etc/system
240000
ndd /dev/tcp
128
ndd /dev/tcp
1024
ndd /dev/tcp
480000
ndd /dev/tcp
7200000
ndd /dev/tcp
3000
ndd /dev/tcp
240000
ndd /dev/tcp
200
ndd /dev/tcp
32768
ndd /dev/tcp
1
ndd /dev/tcp
8129
ndd /dev/tcp
8129
ndd /dev/tcp
Tuned Value
Comments
65536
Process open file descriptors limit;
should account for the expected load
(for the associated sockets, files, and
pipes if any).
0
Controls streams driver queue size;
setting to 0 makes it infinite so the
performance runs won't be hit by lack
of buffer space. Set on clients too.
Note that setting sq_max_size to 0
might not be optimal for production
systems with high network traffic.
60000
Set on clients too.
1024
4096
60000
900000
For high traffic web sites, lower this
value.
3000
If retransmission is greater than
30-40%, you should increase this
value.
10000
3000
1024
Set on clients too.
2
Slightly faster transmission of small
amounts of data.
32768
To increase the transmit buffer.
32768
To increase the receive buffer.
Need help?
Do you have a question about the Sun Java System Web Server 7.0 and is the answer not in the manual?
Questions and answers