[OpenSIPS-Users] number of opensips children

[opensipslist at encambio.com]

Hello Bogdan,

An mer., déc  23, 2009, Bogdan-Andrei Iancu schrieb:
>opensips at encambio.com wrote:
>> An ven., déc 18, 2009, Bogdan-Andrei Iancu schrieb:
>>> To see what processes you have and what they are doing, do:
>>>
>>> opensipsctl fifo ps
>>>
>>   # opensipsctl fifo ps
>>   Process::  ID=0 PID=24975 Type=attendant
>>   Process::  ID=1 PID=24977 Type=SIP receiver udp:123.234.210.1:5060
>>   Process::  ID=2 PID=24978 Type=time_keeper
>>   Process::  ID=3 PID=24979 Type=timer
>>   Process::  ID=4 PID=24980 Type=MI FIFO
>>
>> [...]
>>
>> My gut feeling is that having four UDP listening processes and four
>> TCP listening processes is about right for us, because we only have
>> a handful of UACs participating infrequently (5 calls per day.)
>>   
>Actually that is more than needed - during some performance tests (only 
>simply call relaying) we managed to put 6K cps in a single process.
>
I have eight TCP listeners configured and about sixteen UACs are
connected. I get a ton of these warnings whenever REGISTER or INVITE
messages come in:

  Feb 02 18:17:22 name.host.tld <warning> opensips[02126]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (1)
  Feb 02 18:17:25 name.host.tld <warning> opensips[02126]: WARNING:core:send2child: no free tcp receiver, connection passed to the leastbusy one (1)

Because you mentioned that you benchmarked 6K CPS with a single
process (was it TCP?), I'd like to know if you got as many warnings
as well. One question is:

  What does 'free tcp receiver' mean? I assumed that listening
  TCP ports were free to accept as many connections as needed.

By the way, each of the 16 UACs registered to the 8 TCP listener
processes is avoiding NAT problems by keeping the TCP connection
open by setting the tcp_persistent_flag.

Is OpenSIPS expecting there to be at least one TCP listener process
which is not encumbered by the tcp_persistent_flag?

Regards,
Brian