Difference between revisions of "IPC Locks"

From pressy's brainbackup
Jump to: navigation, search
(Created page with "Small Script to find IPC locks on your system... it might be possible that you see some locks but you should not see many of them (would say more than 10-20 are to much) <pre...")
 
 
Line 11: Line 11:
  
 
If you see too many of them, you might thing about other values in your semaphore settings...
 
If you see too many of them, you might thing about other values in your semaphore settings...
lower process.max-sem-nsems -> Max # of semapores per ID and increase project.max-sem-ids -> Semaphore IDs  ( Queues / Sets )
+
lower process.max-sem-nsems -> Max # of semapores per ID  
 +
and increase project.max-sem-ids -> Semaphore IDs  ( Queues / Sets )
  
 
good start could be:  
 
good start could be:  
 +
<pre>
 
process.max-sem-nsems=(privileged,128,deny)
 
process.max-sem-nsems=(privileged,128,deny)
 
project.max-sem-ids=(privileged,65535,deny)
 
project.max-sem-ids=(privileged,65535,deny)
 
+
</pre>
 
that might bring a higher cpu load but less locks... less waiting for resources...
 
that might bring a higher cpu load but less locks... less waiting for resources...

Latest revision as of 09:22, 30 April 2018

Small Script to find IPC locks on your system... it might be possible that you see some locks but you should not see many of them (would say more than 10-20 are to much)

while true
do
echo "======================================== `date` ======================================="
lockstat -CcwP -n 1000000 -x aggrate=10hz -D 25 -s 50 sleep 10 | grep ipc_lock_internal
sleep 60
done

If you see too many of them, you might thing about other values in your semaphore settings... lower process.max-sem-nsems -> Max # of semapores per ID and increase project.max-sem-ids -> Semaphore IDs ( Queues / Sets )

good start could be:

process.max-sem-nsems=(privileged,128,deny)
project.max-sem-ids=(privileged,65535,deny)

that might bring a higher cpu load but less locks... less waiting for resources...