In a purely hard-coded configuration, without external lookups or other sources of I/O-wait, Kamailio has been shown to handle several tens of thousands of CPS. By the time you hit 20k-30k CPS, you start to run into hardware, scheduler and kernel-side limits that need tweaking.
The actually-existing, real-world throughput of a Kamailio installation is limited by the fact that static configurations aren't very useful for all but the simplest implementations. Most nontrivial applications of Kamailio involve calling out to a database, API or something of that nature at least once during the call processing cycle. Waiting on a response from that source is a synchronous process, and thus blocks Kamailio's (architecturally) limited number of SIP receiver threads.
But even with such limitations in mind, you should still be able to get 200 CPS easily in all but the most exceptionally poorly-designed implementation. 200 CPS isn't very much.
-- Alex
P.S. We specialise in getting thousands of CPS out of Kamailio while still doing _lots_ of SQL queries for routing.
On 06/17/2015 11:17 AM, Jonathan Hunter wrote:
Hi Guys,
Has anyone recently performed tests on kamailio 4.2 running up to 200 CPS?
It would be great to know the hardware requirements for this setup.
Thanks
Jon
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users