Solaris 10 - Performance tuning
Somchai Kanjanapattana
Thanks,
Zulupe
Dennis Clarke
> How to configure the IPC Semaphores and shared memory on Solaris 10?
This is going to hurt .. but .. why would you want to?
Really .. I'd like to know.
In the mean time we can look at docs.sun.com for the kernel parameters that
will go into /etc/system but I still want to know.
Dennis
Alan Hargreaves - Product Technical Support (APAC)
I believe that the answer is, you don't. They are dynamic. I'm sure
someone will correct me if I'm mistaken but I'm sure I remember reading
something about that some time ago.
alan.
--
Alan Hargreaves - http://blogs.sun.com/tpenta
Kernel/VOSJEC/Performance Engineer
Product Technical Support (APAC)
Sun Microsystems
ba...@smaalders.net
In Solaris 10 these are all configured via resource controls;
no setting of parameters or reboots are required. See the
rctladm man page.
An example of the resources that may be controlled this way:
carnot% rctladm -l
process.max-port-events syslog=off [ deny count ]
process.max-msg-messages syslog=off [ deny count ]
process.max-msg-qbytes syslog=off [ deny bytes ]
process.max-sem-ops syslog=off [ deny count ]
process.max-sem-nsems syslog=off [ deny count ]
process.max-address-space syslog=off [ lowerable deny no-signal
bytes ]
process.max-file-descriptor syslog=off [ lowerable deny count ]
process.max-core-size syslog=off [ lowerable deny no-signal
bytes ]
process.max-stack-size syslog=off [ lowerable deny no-signal
bytes ]
process.max-data-size syslog=off [ lowerable deny no-signal
bytes ]
process.max-file-size syslog=off [ lowerable deny file-size
bytes ]
process.max-cpu-time syslog=off [ lowerable no-deny cpu-time
inf seconds ]
task.max-cpu-time syslog=off [ no-deny cpu-time no-obs
inf seconds ]
task.max-lwps syslog=off [ count ]
project.max-contracts syslog=off [ deny count ]
project.max-device-locked-memory syslog=off [ no-basic deny bytes ]
project.max-port-ids syslog=off [ no-basic deny count ]
project.max-shm-memory syslog=off [ no-basic deny bytes ]
project.max-shm-ids syslog=off [ no-basic deny count ]
project.max-msg-ids syslog=off [ no-basic deny count ]
project.max-sem-ids syslog=off [ no-basic deny count ]
project.max-crypto-memory syslog=off [ no-basic deny bytes ]
project.max-tasks syslog=off [ no-basic count ]
project.max-lwps syslog=off [ no-basic count ]
project.cpu-shares syslog=off [ no-basic no-deny no-signal
count ]
zone.max-lwps syslog=off [ no-basic count ]
zone.cpu-shares syslog=off [ no-basic no-deny no-signal
count ]
carnot%
Dennis Clarke
> Dennis Clarke wrote:
>
>> Somchai Kanjanapattana wrote:
>
> I believe that the answer is, you don't. They are dynamic. I'm sure
> someone will correct me if I'm mistaken but I'm sure I remember reading
> something about that some time ago.
that was what my gut feelings told me .. but I wasn't quite sure.
It seemed like those are things we did with Solaris 2.5.1 and possibly as late
as 8.
I do know that I have pounded a Solaris 10 server and it just runs and runs.
Personally I wouldn't touch it
Dennis
Casper H.S. Dik
>How to configure the IPC Semaphores and shared memory on Solaris 10?
You'd be using rctls; and you no longer need to reboot after
changing the parameters.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
Casper H.S. Dik
>I believe that the answer is, you don't. They are dynamic. I'm sure
>someone will correct me if I'm mistaken but I'm sure I remember reading
ome of the SysV limits were dropped in S10 and others were made into
rctls. (And the shmem size, e.g., is now a more reasonable "sum of the
size of shmem segments" rather than a "maximum size for a segment")