<div dir="ltr"><div class="gmail_quote">On Fri, Jul 6, 2012 at 7:27 PM, Stanislav Sinyagin <span dir="ltr"><<a href="mailto:ssinyagin@yahoo.com" target="_blank">ssinyagin@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div style="font-size:10pt;font-family:arial,helvetica,sans-serif"><div><span>OpenVZ and XEN VPS'es are usually fine for quick prototyping and feature tests.</span></div><div><span>Also they would be fine for private PBXes with low call volumes.</span></div>
<div><span>For hundreds of simultaneous calls, it's probably cheaper to rent dedicated hardware servers.</span></div><div><span>On the other side, if you have some smart load balancing, probably you can build a scalable design with VPS'es and eventually migrate to physical servers when volumes are high enough. <br>
</span></div><div><br><span></span></div><div><span>also for a calling card business, probably the most critical CPU resource would be needed for the IVR and real-time billing, but not for the calls themselves.</span></div>
<div><br></div></div></div></blockquote><div><br></div><div><font face="verdana, sans-serif" color="#000099">Thanks Anthony and Stanislav.</font></div><div><font face="verdana, sans-serif" color="#000099"><br></font></div>
<div><font face="verdana, sans-serif" color="#000099">I think I have enough warning along with some encouraging words to build a strategy.</font></div><div><font face="verdana, sans-serif" color="#000099"><br></font></div>
<div><font face="verdana, sans-serif" color="#000099">Thanks again., Now the search for the right IaaS provider begins.</font></div><div><font face="verdana, sans-serif" color="#000099"><br></font></div><div><br></div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:10pt;font-family:arial,helvetica,sans-serif"><div></div><div><span><br></span></div>
<div>
<span>
<br></span></div><div><br><blockquote style="border-left:2px solid rgb(16,16,255);margin-left:5px;margin-top:5px;padding-left:5px"> <div style="font-family:arial,helvetica,sans-serif;font-size:10pt"> <div style="font-family:times new roman,new york,times,serif;font-size:12pt">
<div dir="ltr"> <font face="Arial"> <hr size="1"> <b><span style="font-weight:bold">From:</span></b> A E G <<a href="mailto:all.eforums@gmail.com" target="_blank">all.eforums@gmail.com</a>><br> <b><span style="font-weight:bold">To:</span></b> FreeSWITCH Users Help <<a href="mailto:freeswitch-users@lists.freeswitch.org" target="_blank">freeswitch-users@lists.freeswitch.org</a>> <br>
<b><span style="font-weight:bold">Sent:</span></b> Saturday, July 7, 2012 12:23 AM<br> <b><span style="font-weight:bold">Subject:</span></b> Re: [Freeswitch-users] RTP delay > 100ms by performance testing with freeswitch as trancoding device SILK to G711a<br>
</font> </div><div><div class="h5"> <br>
<div><div dir="ltr"><div>On Fri, Jul 6, 2012 at 5:43 PM, Anthony Minessale <span dir="ltr"><<a rel="nofollow" href="mailto:anthony.minessale@gmail.com" target="_blank">anthony.minessale@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I would be insane to endorse using it in a virtual world. The support<br>
expectations would consume the rest of my life.<br>
I try to make the code work well on real boxes and if it works on<br>
virtual ones then that's a bonus =D<br>
<br>
We have good luck with openVZ since its a single real kernel and<br>
virtual runtimes but either way we do not recommend it so its a use at<br>
your own risk kind of thing.<br>
<div><div><br></div></div></blockquote><div><br></div><div><font color="#3333ff" face="verdana, sans-serif">Yup agree and acknowledge that you wouldn't endorse or offer to support it, and nor should you. Simply trying to pick your (and anyone else who wants to chime in) brain on the topic. Totally PoC'ing it at my own risk :)</font></div>
<div><font color="#3333ff" face="verdana, sans-serif"><br></font></div><div><font color="#3333ff" face="verdana, sans-serif">So, in that spirit, just one last message about it. Just like sharing the experience with OpenVZ, let's just say that I am insane and I still want to try it in a private cloud. Would you say the resource consumption of FS (assuming it's just receiving the call, having it routed by a custom routing engine via ESL, and switching it) be more than that in the "real" world for the same call volume barring any clock sync/skew/jitter issues? Would something like Cloudstack on hardware (like the one you recommended earlier) with a FS VM with 12 vcpu cores, 24GB RAM and DAS be able to handle something like 300-400 concurrent calls or am I out of my mind?</font></div>
<div><font color="#3333ff" face="verdana, sans-serif"><br></font></div><div><font color="#3333ff" face="verdana, sans-serif">Thx </font></div><div><br></div><div> </div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>
On Fri, Jul 6, 2012 at 3:59 PM, A E G <<a rel="nofollow" href="mailto:all.eforums@gmail.com" target="_blank">all.eforums@gmail.com</a>> wrote:<br>
> Yup got that, and are you saying the same is applicable and true even if one<br>
> was to try and run FreeSWITCH on a private cloud or in a virtual<br>
> environment? assuming of course that those tips would then apply to the<br>
> machine on which the Hypervisor will run.<br>
><br>
> Just trying to get a handle on whether running FreeSWITCH to do something<br>
> like wholesale or calling card traffic in a purely virtual environment is /<br>
> has proven to work. You probably know the most in terms of all different<br>
> environments people are running FS in, and if you (or they) have pointers<br>
> specific to it being run in a virtual environment.<br>
><br>
> Thanks so much<br>
><br>
> On Fri, Jul 6, 2012 at 12:54 PM, Anthony Minessale<br>
> <<a rel="nofollow" href="mailto:anthony.minessale@gmail.com" target="_blank">anthony.minessale@gmail.com</a>> wrote:<br>
>><br>
>> Like I said "Really Really Nice Motherboard", as many CPU as<br>
>> possible/affordable, and a good chunk of RAM.<br>
>> Motherboard is the most important, a cheap motherboard with a ton of<br>
>> cores is a waste.<br>
>><br></div></div></blockquote></div></div>
</div><br></div></div><div class="im"><br></div></div></div></blockquote></div></div></div></blockquote></div></div>