Kamailio is using spin locks (for mutexes) and that can cause high cpu on some 
systems. I am not very familair with dmq internals, but it looks like it uses 
mutexes to trigger the presence of a new task for its worker processes, meaning 
that a worker stays in mutex-get operation (spinning), until a new task 
arrives. Maybe @charlesrchance can shed more light here.

Of course, this high cpu can show up in case of a deadlock, but if you say all 
works fine whether there is traffic to handle, then is not a deadlock.

The option is to compile to use POSIX semaphores -- the Makefile.defs needs to 
be changed and all recompiled.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
sr-dev mailing list

Reply via email to