Hi Jayesh,
There are 2 aspects here :
- first, configure proper limits when starting OpenSIPS - like max
number of fds per process, etc.
- secondly, when comes to opensips itself, you need to look into :
* enough memory (TCP uses a lot)
* set proper timeouts in TCP (connect, write, read timeouts) to
avoid blocking
* properly handle the TCP lifetime to get to a compromise
between the number of ongoing connections and seting/closing connections
* really good control over when OpenSIPS should open new TCP
conns - you can do this from script, depending on the target (like never
try to open conns towards end-user, let them connect to you).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 10.09.2014 14:55, Jayesh Nambiar wrote:
Hello,
I am in process of designing opensips which can handle a million
users, hypothetically 200,000 registrations and 500CPS capacity. I've
been reading a lot and learnt that TCP design is blocking and not
suitable for huge volumes.
My requirement was to have TLS between endpoints and Opensips and
hence riding over TCP is the only option. I needed some expert
suggestions on what things should be taken care of when planning a
large deployment over TCP.
I have built similar stuff on UDP and I trust it heavily as it has
performed perfectly as expected. But when it comes to TCP I'm a bit
clueless.
I've read about lot of global parameters that is now available for
asynchrous tcp operations. Is it really helpful when planning for
scalable environments??
Thanks for any suggestions !!
W/regards,
Jayesh
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
