| Roman:
The following information is available in the System Tuning and Performance
Management Guide
under section B.12. These can be set in /etc/sysconfigtab and will all fall
under the
"proc:" header. For instance on my machine I have this:
#
# Memory Configuration
#
vm:
vm-maxvas = 2147483648
vm-vpagemax = 65536
proc:
max-per-proc-data-size = 2147483648
max-per-proc-address-space = 2147483648
per-proc-data-size = 1073741824
If you have any questions, please write back.
Gerrit Saylor
Alpha Developer Support
---------------
B.12 Process Subsystem Attributes
autonice (autonice)
When set, applications that use more than 600 seconds of CPU time will
automatically increase their nice
values
(that is, lower their scheduling priorities).
Default value: 0 (off)
autonice-penalty
The nice value applied to a process after it has exceeded autonice-time
seconds of CPU time.
Default value: 4
autonice-time
The time in seconds of total CPU time a process can run before the
autonice-penalty is applied as a nice
value to
the process.
Default value: 600
give-boost (give_boost)
When set on (1), this attribute give a priority boost to processes that
have just woken up from a block I/O
operation. This reduces I/O latency and makes the system generally more
responsive.
max-per-proc-address-space (vm_initial_limit_vas.rlim_max)
max-per-proc-data-size (vm_initial_limit_data.rlim_max)
max-per-proc-stack-size (vm_initial_limit_stack.rlim_max)
Maximum values for the current limits of the attributes
per-proc-address-space, per-proc-data-size,
and per-proc-stack-size. The current limits can be increased at run time by
means of the setrlimit(2)
system call or the ulimit(3) C library call. The current limits cannot be
expanded beyond the values
established
by the "max-per-proc-*" attributes.
max-proc-per-user (maxuprc)
The maximum limit of processes (tasks) a user can create. (The superuser is
not affected.)
Default value: 64
max-threads-per-user (maxuthreads)
The maximum limit of threads a user can create. (The superuser is not
affected.)
maxusers (maxusers)
The maxusers attribute is used to tune several system parameters to
increase the number of users who can
theoretically use a system simultaneously. Changing the value of this
attribute generates changes to the
values of
taskmax, threadmax, and min_free_vnodes, to name a few.
Default value: Specified in the system configuration file.
ncallout (ncallout)
Not used. Obsolete.
ncallout_alloc_size
The low watermark for the amount of memory used for timeout tables. The
value of this attribute is adjusted
dynamically.
Tuning Suggestions: Not tunable.
open-max-hard (open_max_hard)
open-max-soft (open_max_soft)
The number of per-process file descriptors. Use the getdtablesize system
call to obtain the current limit.
The
value of open_max_soft is the default per-process limit. A process can
increase its soft limit up to its
hard limit
using setrlimit. The default hard and soft limits must be at least 64, and
less than or equal to
OPEN_MAX_SYSTEM in param.h.
Default value: 4096 (for both attributes)
per-proc-address-space (vm_initial_limit_vas.rlim_cur)
per-proc-data-size (vm_initial_limit_data.rlim_cur)
per-proc-stack-size (vm_initial_limit_stack.rlim_cur)
The current upper limits of the respective resources. For example, a user
stack cannot exceed the size set
by the
per-proc-stack-size attribute.
round-robin-switch-rate (round_robin_switch_rate)
The number of context switches per second that can occur between equal
priority processes. The lower the
number,
the less the system timeslices; the higher the number, the more the system
timeslices.
sched-min-idle (sched_min_idle)
The amount of time that a thread must remain idle on a multiprocessor
system before it is eligible to
migrate to
another processor. This attribute is used to tune the "soft affinity"
algorithm on multiprocessor systems.
This
enables a process to stay where it last ran and thereby optimize its use of
any data or instructions that it
had
brought into cache memory.
The sched-min-idle attribute is used by the Scheduler on multiprocessor
systems; it has no effect on single
CPU systems.
task-max (taskmax)
The maximum number of tasks that can run simultaneously on the system.
Default value: 20 + 8 * maxusers
thread-max (threadmax)
The maximum number of kernel threads that can run simultaneously on the
system.
Default value: 2 * taskmax
|