> Setting this value as mentioned from Markus D�hr we decreased
> our cpu usage from avg. 50% to 20% (again thanks to Markus ;-) ).
Wow, wasn't aware that this is also a CPU issue :-) Nice to hear.
The values are only upper hard limits. It's analogue to Solaris' /etc/system
settings
set semsys:seminfo_semmap=64
set semsys:seminfo_semmni=4096
set semsys:seminfo_semmns=4096
set semsys:seminfo_semmnu=4096
set semsys:seminfo_semume=64
set shmsys:shminfo_shmmin=100
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=100
On Linux:
kernel.sem: max_sem_per_id max_sem_total max_ops_sem_call max_sem_ids
max_sem_per_id: maximum number of semaphores identifiers (sets)
max_sem_total : maximum number of semaphores systemwide
max_ops_sem_call: maximum operations per semop() call
max_sem_ids: maximum number of semaphores per array
So these are only upper limits. See also /usr/src/linux/include/sem.h. In
the 2.2 series you had to change these values in the sourcecode and
recompile the kernel, now it's dynamically changable via sysctl and is IMHO
the only OS that will be able to change the values without a reboot :-)
Greetz,
SIEGENIA-AUBI KG
Informationswesen
i.A.
Markus D�hr
SAP-CC/BC, SAPDB-DBA
Tel.: +49 6503 917-152
Fax: +49 6503 917-7152
E-Mail: [EMAIL PROTECTED]
Internet: http://www.siegenia-aubi.com
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
