[Spce-user] virtualizing sip:provider CE

[William Fulton]

Is anyone using the AWS build in production?  I have been testing, but if it won’t scale it doesn’t make sense to use.  Any feedback based on first-hand experience would be appreciated.

 

Thank you,

Bill

 

From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Norbert Piper
Sent: Wednesday, May 18, 2016 11:47 AM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] virtualizing sip:provider CE

 

Hi together.

We are virtualisation specialist. And we have tried differnt kind of hypervisors like xen vmware promox and hyperv. At least we got stuck on hyperV. All hypervisors have different bottlenecks. Maybe we can make a litte projekt for virtualisation. As we are interssted in a HA kamailio cluster too ,  but we have to admit that theres a leak if know how 

Cheer 
Norbert

Sent by MailWise <http://www.mail-wise.com/installation/4>  – Your emails, with style.:)



-------- Ursprüngliche Nachricht --------
Von: Christian Rohmann <crohmann at netcologne.de>
Gesendet: Wednesday, May 18, 2016 04:38 PM
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] virtualizing sip:provider CE



On 05/17/2016 04:31 PM, Andreas Granig wrote:
> The number of regs it can do without calls is somewhere around 80
> regs/sec, but if you add some calls, it degrades quite quickly.

Did you further narrow down what the reason for the current performance
limits is? Some profiling of where the bottleneck actually is, so which
component maxes out first, could surely help to scale or improve the
right components (software or hardware).

Especially all those (incoming) registrations, which currently go
persistently into a relational (MySQL) database, are quite expensive for
data (or better called "state") that could be recreated at any time
would the whole cluster ever crash or explode. Just restart and have the
clients re-register ... nothing of value (actual call state or even
CDRs) would be lost.

Cluster-wide replication via the likes of redis or hazelcast or some
other replicated, in-memory database might completely remove this
bottleneck of registrations and have NGCP scale with the actual calls
which are handled (and worth having their state stored persistently
somewhere).



Regards

Christian
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160519/4896c5ec/attachment-0001.html>