[SR-Users] multi-process not multi-threading

[Alex Balashov]

Generally speaking, no, it's not worth it. Speaking specifically, there's some disagreement on that topic, as past discussions on the list evidence.

My personal experience has been diminishing returns when n(sip workers) > n(nproc).

--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States

Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

Sent from my BlackBerry.
  Original Message  
From: Daniel Tryba
Sent: Friday, August 14, 2015 10:47
To: sr-users at lists.sip-router.org
Reply To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] multi-process not multi-threading

On Friday 14 August 2015 09:09:44 Alex Balashov wrote:
> Kamailio technically uses multiple forked processes, not multiple threads,
> but the end-result is the same. And multiple processes certainly run on
> multiple cores.

My guess is Ali is asking a different question: 
If there are n cpus and m threads, how many messages can be handled 
concurrently.

The answer is that there is no direct relation, but is it worth having m>n?


_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users at lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users