<?xml version="1.0" encoding="utf-8"?>
<!-- If you are running a bot please visit this policy page outlining rules you must respect. https://www.livejournal.com/bots/ -->
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:lj="https://www.livejournal.com">
  <id>urn:lj:livejournal.com:atom1:openvz</id>
  <title>OpenVZ</title>
  <subtitle>OpenVZ</subtitle>
  <author>
    <name>OpenVZ</name>
  </author>
  <link rel="alternate" type="text/html" href="https://openvz.livejournal.com/"/>
  <link rel="self" type="text/xml" href="https://openvz.livejournal.com/data/atom"/>
  <updated>2009-12-10T12:35:35Z</updated>
  <lj:journal userid="9392309" username="openvz" type="community"/>
  <link rel="service.feed" type="application/x.atom+xml" href="https://openvz.livejournal.com/data/atom" title="OpenVZ"/>
  <entry>
    <id>urn:lj:livejournal.com:atom1:openvz:30232</id>
    <author>
      <name>dowdle</name>
    </author>
    <lj:poster user="dowdle" userid="9725912"/>
    <link rel="alternate" type="text/html" href="https://openvz.livejournal.com/30232.html"/>
    <link rel="self" type="text/xml" href="https://openvz.livejournal.com/data/atom/?itemid=30232"/>
    <title>An OpenVZ Experiment, 1 year later</title>
    <published>2009-12-10T12:35:35Z</published>
    <updated>2009-12-10T12:35:35Z</updated>
    <content type="html">Some of you may recall that last December I did an &lt;a href="http://www.montanalinux.org/openvz-experiment.html" target="_blank" rel="nofollow"&gt;experiment&lt;/a&gt; where I created 638 OpenVZ containers on an HP Proliant DL380 G5 machine with dual quad-core CPUs and 32GB of RAM.  I stopped there because I ran into an &lt;a href="http://bugzilla.openvz.org/show_bug.cgi?id=1245" target="_blank" rel="nofollow"&gt;error&lt;/a&gt;.  Well, one of the OpenVZ / Parallels developers &lt;a href="http://www.montanalinux.org/openvz-experiment.html#comment-23738" target="_blank" rel="nofollow"&gt;suggested a fix&lt;/a&gt; back in July both as a comment to my article and as a &lt;a href="http://bugzilla.openvz.org/show_bug.cgi?id=1245#c6" target="_blank" rel="nofollow"&gt;comment&lt;/a&gt; to the bug report... but somehow I overlooked it until I ran across it again the other day when cleaning out my email.&lt;br /&gt;&lt;br /&gt;I finally got a chance to give it a try and sure enough it removed the limit I had run into (the sysctl kernel.pid_max default setting being too low) and I verified it by creating 700 containers.&lt;br /&gt;&lt;br /&gt;At first I decided to stop there but then I got an email from Kir asking if disk space was going to end up being my real limitation.  I'm wondering if Kir has seen other experiments that go to this extreme or if he is simply a good guesser (with some inside information)?  Anyway, I decide to bump it up to 1,000 containers.  Sure enough, the machine is handling it just fine.&lt;br /&gt;&lt;br /&gt;I didn't do a completely new write up, I just wrote a few more comments to the original article and you can find it here:&lt;br /&gt;&lt;br /&gt;An OpenVZ Experiment - How many containers?&lt;br /&gt;&lt;a href="http://www.montanalinux.org/openvz-experiment.html" target="_blank" rel="nofollow"&gt;http://www.montanalinux.org/openvz-experiment.html&lt;/a&gt;</content>
  </entry>
</feed>
