<div dir="ltr">On Wed, Apr 17, 2013 at 10:50 PM, Wolf Halton <span dir="ltr"><<a href="mailto:wolf.halton@gmail.com" target="_blank">wolf.halton@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p>I have been testing openvz servers for over a year. Work well for simple web services like drupal and less well for i/o-heavy apps like evergreen-ils.</p>
<p>We don't offer service to gen public, but I would be confident using openvz for production PaaS.<br>
easy to back up, easy to use. </p></blockquote><div style>When run correctly, OpenVZ is ok, but it seems to be much easier to run incorrectly. "Burstable" RAM usually means they fairly heavily overprovision (at least down to your base RAM). OpenVZ also offers less consistent isolation between VMs. So, on a well-managed host with "cooperative" neighbors, OpenVZ is not bad. But on someone selling on LEB for $2/mo, yeah, you're gonna have a bad time.</div>
<div style><br></div><div style>So while it's probably not fair that I won't use a VPS provider who uses OpenVZ, it's become one of my "rules of thumb" for VPS providers. </div></div><br><br clear="all">
<div><br></div>-- <br>David Tomaschik<br>OpenPGP: 0x5DEA789B<br><a href="http://systemoverlord.com" target="_blank">http://systemoverlord.com</a><br><a href="mailto:david@systemoverlord.com" target="_blank">david@systemoverlord.com</a>
</div></div>