[OpenSIPS-Users] Scalability and radiusclient-ng

[Alex Massover]

Hi!

I have a couple of questions regarding OpenSIPS scalability.

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?

Second question is scalability of radiusclient-ng? Does radiusclient-ng able to take care of concurrent requests or it works sequentially? I noticed that it use .seq file to synchronize request. From my understanding it suggests that radiusclient-ng works with requests one by one.
I receive the following error at 10 cps:
13:42:57 y-dev5 /usr/sbin/opensips[10887]: rc_get_seqnbr: couldn't get lock after 10 tries: /var/run/opensips/opensips_radius.seq
Does it mean that acc_radius request failed? Is there any way to get it more robust?

--
Best Regards,
Alex Massover



 
 
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20080908/94ff095f/attachment.htm