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
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
Hi Alex, Thanks for the response. No understood, I am aware kamailio is all about thousands of calls per second, I just wondered if it had been bench marked, as many companies unfamiliar with kamailio like these things :). I will look at it from the database angle as there will be the same amount of queries. thanks Jon
Date: Wed, 17 Jun 2015 11:21:06 -0400 From: abalashov@evaristesys.com To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Performance Tests/Hard Recommendations kamailio 4.2 -200CPS
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
-- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
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
On 06/17/2015 11:28 AM, Jonathan Hunter wrote:
No understood, I am aware kamailio is all about thousands of calls per second, I just wondered if it had been bench marked, as many companies unfamiliar with kamailio like these things :).
It's probably been a while since anyone's done some formal benchmarking, but anecdotally, I can say that we can pull 2000-3000 CPS even with considerable external I/O dependencies. 200 CPS should be a no-brainer for a redirect server.
Jonathan Hunter writes:
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.
performance depends, e.g., on how many db queries your script uses when it process one call. if no db queries are done, 200 cps is not much.
-- juha
Hi Juha, I am looking at a SIP redirect server, so I would scope on potentially 1 DB query per call to get routing information. Thanks Jon
Date: Wed, 17 Jun 2015 18:22:56 +0300 To: sr-users@lists.sip-router.org From: jh@tutpro.com Subject: [SR-Users] Performance Tests/Hard Recommendations kamailio 4.2 -200CPS
Jonathan Hunter writes:
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.
performance depends, e.g., on how many db queries your script uses when it process one call. if no db queries are done, 200 cps is not much.
-- juha
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
I currently have a 302 LCR redirect platform that we use for dialer traffic that utilizes a single MySQL server (with a redundant backup of course), does 17 queries of varying complexity for various routing data decisions (LRN lookup, LERG data retrieval, routing table lookups, and so on), and has been benchmarked (using multiple systems running multiple copies of sipp) at over 8000 cps with no issues.
The proxy itself is running on a Dell R610 with 32GB of ram and 2 x Xeon X5570's (4 cores, 2.93GHz, with HT) and reaches around 400-500% aggregate cpu usage at full load.
Brooks Bridges | Sr. Voice Services Engineer O1 Communications 5190 Golden Foothill Pkwy El Dorado Hills, CA 95762 office: 916.235.2097 | main: 888.444.1111, Option 2 email: bbridges@o1.commailto:bbridges@o1.com | web: www.o1.comhttp://www.o1.com/
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Jonathan Hunter Sent: Wednesday, June 17, 2015 8:32 AM To: Kamailio SER - Users Mailing List Subject: Re: [SR-Users] Performance Tests/Hard Recommendations kamailio 4.2 -200CPS
Hi Juha,
I am looking at a SIP redirect server, so I would scope on potentially 1 DB query per call to get routing information.
Thanks
Jon
Date: Wed, 17 Jun 2015 18:22:56 +0300 To: sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org From: jh@tutpro.commailto:jh@tutpro.com Subject: [SR-Users] Performance Tests/Hard Recommendations kamailio 4.2 -200CPS
Jonathan Hunter writes:
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.
performance depends, e.g., on how many db queries your script uses when it process one call. if no db queries are done, 200 cps is not much.
-- juha
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Great thanks Guys that perfect. Many thanks Jon
From: bbridges@o1.com To: sr-users@lists.sip-router.org Date: Wed, 17 Jun 2015 15:43:31 +0000 Subject: Re: [SR-Users] Performance Tests/Hard Recommendations kamailio 4.2 -200CPS
I currently have a 302 LCR redirect platform that we use for dialer traffic that utilizes a single MySQL server (with a redundant backup of course), does 17 queries of varying complexity for various routing data decisions (LRN lookup, LERG data retrieval, routing table lookups, and so on), and has been benchmarked (using multiple systems running multiple copies of sipp) at over 8000 cps with no issues.
The proxy itself is running on a Dell R610 with 32GB of ram and 2 x Xeon X5570’s (4 cores, 2.93GHz, with HT) and reaches around 400-500% aggregate cpu usage at full load.
Brooks Bridges | Sr. Voice Services Engineer O1 Communications 5190 Golden Foothill Pkwy
El Dorado Hills, CA 95762 office: 916.235.2097 | main: 888.444.1111, Option 2 email: bbridges@o1.com | web: www.o1.com
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Jonathan Hunter
Sent: Wednesday, June 17, 2015 8:32 AM
To: Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Performance Tests/Hard Recommendations kamailio 4.2 -200CPS
Hi Juha,
I am looking at a SIP redirect server, so I would scope on potentially 1 DB query per call to get routing information.
Thanks
Jon
Date: Wed, 17 Jun 2015 18:22:56 +0300
To: sr-users@lists.sip-router.org
From: jh@tutpro.com
Subject: [SR-Users] Performance Tests/Hard Recommendations kamailio 4.2 -200CPS
Jonathan Hunter writes:
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.
performance depends, e.g., on how many db queries your script uses when
it process one call. if no db queries are done, 200 cps is not much.
-- juha
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
_______________________________________________ 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
On Wednesday 17 June 2015 15:31:33 Jonathan Hunter wrote:
I am looking at a SIP redirect server, so I would scope on potentially 1 DB query per call to get routing information.
I have a couple for virtual redirect servers that do something like 200 cps with multiple mysql queries (routing, tollfraud) that use less than 50Mhz on average according to vmware, response time from invite to ack is between 0.004 and 0.008 seconds. No caching of results anywhere (not even in the database servers).