<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p dir="ltr">Hi together.</p>
<p dir="ltr">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
</p>
<p dir="ltr">Cheer <br>
Norbert</p>
<p dir="ltr">Sent by <a href="http://www.mail-wise.com/installation/4">MailWise</a> – Your emails, with style.:)<br>
</p>
<br>
<br>
-------- Ursprüngliche Nachricht --------<br>
Von: Christian Rohmann <crohmann@netcologne.de><br>
Gesendet: Wednesday, May 18, 2016 04:38 PM<br>
An: spce-user@lists.sipwise.com<br>
Betreff: Re: [Spce-user] virtualizing sip:provider CE<br>
<br>
<p><br>
<br>
On 05/17/2016 04:31 PM, Andreas Granig wrote:<br>
> The number of regs it can do without calls is somewhere around 80<br>
> regs/sec, but if you add some calls, it degrades quite quickly.<br>
<br>
Did you further narrow down what the reason for the current performance<br>
limits is? Some profiling of where the bottleneck actually is, so which<br>
component maxes out first, could surely help to scale or improve the<br>
right components (software or hardware).<br>
<br>
Especially all those (incoming) registrations, which currently go<br>
persistently into a relational (MySQL) database, are quite expensive for<br>
data (or better called "state") that could be recreated at any time<br>
would the whole cluster ever crash or explode. Just restart and have the<br>
clients re-register ... nothing of value (actual call state or even<br>
CDRs) would be lost.<br>
<br>
Cluster-wide replication via the likes of redis or hazelcast or some<br>
other replicated, in-memory database might completely remove this<br>
bottleneck of registrations and have NGCP scale with the actual calls<br>
which are handled (and worth having their state stored persistently<br>
somewhere).<br>
<br>
<br>
<br>
Regards<br>
<br>
Christian<br>
_______________________________________________<br>
Spce-user mailing list<br>
Spce-user@lists.sipwise.com<br>
https://lists.sipwise.com/listinfo/spce-user<br>
</p>
</body>
</html>