Changed Parameters
These parameters changed or were corrected.
maxusers
The following section changed.
- Range
-
1 to 2048
to:
- Range
-
1 to 2048, based on physical memory without any setting in the /etc/system file.
1 to 4096, if set in the /etc/system file.
pages_pp_maximum
The following sections changed.
- Default
-
Maximum of the triplet (200, tune_t_minarmem + 100, [10% of memory available at boot time])
to:
- Default
-
The greater of (tune_t_minarmem + 100 and [4% of memory available at boot time + 4 Mbytes])
- Range
-
Default value to no more than 20% of physical memory. The systems does no enforcement of this range other than that described in the Validation section.
to:
- Range
-
Minimum value enforced by the system is tune_t_minarmem + 100. The system does not enforce a maximum value.
- Dynamic?
-
Yes, unless dynamic reconfiguration operations that add or delete memory occur. At that point, the value is reset to whatever was provided in the /etc/system file or was calculated.
- Validation
-
Maximum of the quadruplet (200, tune_t_minarmem + 100, [10% of memory available], and the value from /etc/system). No message is displayed if the value from /etc/system is increased. Done only at boot time.
to:
- Validation
-
If the value specified in the /etc/system file or the calculated default is less than tune_t_minarmem + 100, the value is reset to tune_t_minarmem + 100.
No message is displayed if the value from the /etc/system file is increased. Done only at boot time, and during dynamic reconfiguration operations that involve adding or deleting memory.
- When to Change
-
When memory locking requests or attaching to a shared memory segment with the SHARE_MMU flag fails, yet the amount of memory available seems to be sufficient. Keeping 10% of memory free on a 32-Gbyte system might be excessive.
Excessively large values can cause memory locking requests to fail unnecessarily.
to:
- When to Change
-
When memory locking requests or attaching to a shared memory segment with the SHARE_MMU flag fails, yet the amount of memory available seems to be sufficient.
Excessively large values can cause memory locking requests to fail unnecessarily.
rlim_fd_max
The following section changed for releases prior to the Solaris 9 release.
- Default
-
1024
to:
- Default
-
65,536
segkpsize
The following section changed for the Solaris 9 8/03 release. This section was also moved to the General Parameters section of Chapter 2, Solaris Kernel Tunables.
- Units
-
Mbytes
to
- Units
-
8–Kbyte pages
segspt_minfree
The following section changed.
- Range
-
0 to 32,767
to:
- Range
-
0 to 50% of physical memory.
shmsys:shminfo_shmseg
The following section changed.
- Description
-
Limit on the number of shared memory segments that any one process can create.
to:
- Description
-
Limit on the number of shared memory segments that any one process can attach.
shmsys:shminfo_shmmax
The following sections changed.
- Description
-
Maximum size of system V shared memory segment that can be created. This parameter is an upper limit that is checked before the system sees if it actually has the physical resources to create the requested memory segment.
to:
- Description
-
Maximum size of system V shared memory segment that can be created. This parameter is an upper limit that is checked before the system sees if it actually has the physical resources to create the requested memory segment.
Attempts to create a shared memory section whose size is zero or whose size is larger than the specified value will fail with an EINVAL error.
- Default
-
1,048,576
to:
- Default
-
8,388,608
The following sections changed in the Solaris 9 8/03 release.
- Description
-
Maximum size of system V shared memory segment that can be created. This parameter is an upper limit that is checked before the system sees if it actually has the physical resources to create the requested memory segment.
Attempts to create a shared memory section whose size is zero or whose size is larger than the specified value will fail with an EINVAL error.
to
- Description
-
Maximum size of system V shared memory segment that can be created. This parameter is an upper limit that is checked before the application sees if it actually has the physical resources to create the requested memory segment.
Attempts to create a shared memory section whose size is zero or whose size is larger than the specified value will fail with an EINVAL error.
This parameter specifies only the largest value the operating system can accept for the size of a shared memory segment. Whether the segment can be created depends entirely on the amount of swap space available on the system and, for a 32-bit process, whether there is enough space available in the process's address space for the segment to be attached.
- Range
-
0 - MAXINT on 32-bit systems, 0 – MAXINT64 on 64-bit systems
to
- Range
-
0 - MAXUINT32 on 32-bit systems, MAXUINT64 on 64-bit systems
sq_max_size
- Range
-
1 to 0 (unlimited)
to
- Range
-
0 (unlimited) to MAXINT
- When to Change
-
When NCA is running on a system with a lot of memory, increase this parameter to allow drivers to queue more packets of data. If a server is under heavy load, increase this parameter so modules and drivers may process more data without dropping packets or getting backlogged.
to
- When to Change
-
When NCA is running on a system with a lot of memory, increase this parameter to allow drivers to queue more packets of data. If a server is under heavy load, increase this parameter so modules and drivers may process more data without dropping packets or getting backlogged.
Note –sq_max_size=0 is intended only for benchmarks or testing environments.
Solaris 8 and later releases – Do not set this parameter to 0 on production systems. If you need to change this parameter, gradually increase this value and monitor the system.
Solaris 7 and earlier releases – Do not set this parameter to 0 on production systems. If you need to change this parameter, gradually increase this value to a maximum of 100, and monitor the system.
tmpfs:tmpfs_maxkmem
The following section changed.
- Default
-
to:
- Default
-
One page or 4% of physical memory, whichever is greater.
tmpfs:tmpfs_minfree
This parameter was corrected. The following section changed:
- Units
-
Bytes
to:
- Units
-
Pages
tcp_rexmit_interval_max
The following section changed.
- Range
-
1 millisecond to 20 seconds
to:
- Range
-
1 millisecond to 2 hours
tcp_slow_start_initial
This parameter was corrected.
For information, see tcp_slow_start_initial.
tcp_conn_req_max_q0
The following section changed:
- When to Change
-
For applications, such as web servers that might receive excessive connection requests, you can increase the default value to match the incoming rate.
The following explains the relationship between tcp_conn_req_max_q0 and the maximum number of pending connections for each socket.
When a connection request is received, TCP first checks if the number (N) of pending TCP connections (three-way handshake is done) waiting to be accepted exceeds the maximum for the listener. If the connections are excessive, the request is denied. If the number of connections is allowable, then TCP checks if the number of incomplete pending TCP connections exceeds the sum of N and tcp_conn_req_max_q0. If it does not, the request is accepted. Otherwise, the oldest incomplete pending TCP request is dropped.
to:
- When to Change
-
For applications, such as web servers that might receive excessive connection requests, you can increase the default value to match the incoming rate.
The following explains the relationship between tcp_conn_req_max_q0 and the maximum number of pending connections for each socket.
When a connection request is received, TCP first checks if the number of pending TCP connections (three-way handshake is done) waiting to be accepted exceeds the maximum (N) for the listener. If the connections are excessive, the request is denied. If the number of connections is allowable, then TCP checks if the number of incomplete pending TCP connections exceeds the sum of N and tcp_conn_req_max_q0. If it does not, the request is accepted. Otherwise, the oldest incomplete pending TCP request is dropped.
Removal of sun4d Support
The sun4d platform is not supported in the Solaris 9 release. The following parameters were modified to reflect the removal of sun4d support:
- © 2010, Oracle Corporation and/or its affiliates