[OpenSIPS-Users] Scalability and radiusclient-ng
Iñaki Baz Castillo
ibc at in.ilimit.es
Mon Sep 8 16:27:15 CEST 2008
El Monday 08 September 2008 16:12:11 Alex Massover escribió:
> If I understood correctly a single child of OpenSIPS is able to handle 1
> transaction simultaneously? So if I have 10 concurrent transactions I need
> at least 10 children, otherwise transactions will wait for a free child to
> take care?
Note that a child doesn't handle an entire transaction. It can occurs, and
it's the most probable, that the reply is handled by other child.
Also the childs don't manage transactions but transport level connections (or
UDP datagrams). This is: a child can receive a request, process it, create
branches and send them, and after it, the child can receive other different
request over the same TCP connection and manage it without waiting for the
previous transaction finished (note that an INVITE transaction can be alive
more than 1 minute).
So I think you are wrong when associate "childs" and "transactions". It's more
correct if you associate "childs" and "connections"/"datagram arrival".
--
Iñaki Baz Castillo
ibc at in.ilimit.es
More information about the Users
mailing list