logevent_max_q_sz
| Description | Maximum number of system
events allowed to be queued waiting for delivery to the syseventd daemon. Once the size of the system event queue reaches this limit,
no other system events will be allowed on the queue.
| | Data Type | Integer
| | Default | 2000
| | Range | 0 to MAXINT
| | Units | System events
| | Dynamic? | Yes
| | Validation | The sysevent framework
checks this value every time a system event is generated by ddi_log_sysevent(9F)
and sysevent_post_event(3SYSEVENT).
| | When to Change | When error log messages
indicate that a system event failed to be logged, generated, or posted.
| | Commitment Level | Unstable
|
segkpsize
| Description | Specify the amount of
kernel pageable memory available. This memory is used primarily for kernel
thread stacks. Increasing this number allows either larger stacks for the
same number of threads or more threads. This parameter can only be set on
systems running 64-bit kernels. Systems running 64-bit kernels use a
default stack size of 24 Kbytes.
| | Data Type | Unsigned long
| | Default | 64-bit kernels, 2
Gbytes
32-bit kernels, 512 Mbytes
| | Range | 64-bit kernels, 512
Mbytes - 24 Gbytes
32-bit kernels, 512 Mbytes
| | Units | 8-Kbyte pages
| | Dynamic? | No
| | Validation | Value is compared to
minimum and maximum sizes (512 Mbytes and 24 Gbytes for 64-bit systems) and
if smaller than the minimum or larger than the maximum, it is reset to 2 Gbytes
and a message to that effect is displayed.
The actual size used in creation of the cache is the lesser of the value
specified in segkpsize after the constraints checking and
50% of physical memory.
| | When to Change | This is one of the
steps necessary to support large numbers of processes on a system. The default
size of 2 Gbytes, assuming at least 1 Gbyte of physical memory is present,
allows creation of 24-Kbyte stacks for more than 87,000 kernel threads.
The size of a stack in a 64-bit kernel is the same whether the process is
a 32-bit process or a 64-bit process. If more than this number is needed, segkpsize can be increased assuming sufficient physical memory exists.
| | Commitment Level | Unstable
| | Change History | For information,
see segkpsize (Solaris 9 12/02 Release).
|
fsflush and Related Tunables
This section describes fsflush and related tunables.
fsflush
The system daemon, fsflush, runs periodically to
do three main tasks:
Frequency of invocation, whether the memory scanning is executed, whether
the file system data flushing occurs, and the frequency with which it will
occur are configurable.
For most systems, memory scanning and file system metadata syncing are
the dominant activities for fsflush. Depending on system
usage, memory scanning can be of little use or consume too much CPU time.
tune_t_fsflushr
| Description | Specifies the number
of seconds between fsflush invocations.
| | Data Type | Signed integer
| | Default | 5
| | Range | 1 to MAXINT
| | Units | Seconds
| | Dynamic? | No
| | Validation | If the value is less
than or equal to zero, the value is reset to 5 and a warning message is displayed.
This check is only done at boot time.
| | When to Change | See autoup below.
| | Commitment Level | Unstable
|
|
Previous