<?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/  -->
<rss version='2.0'  xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:media='http://search.yahoo.com/mrss/' xmlns:atom10='http://www.w3.org/2005/Atom'>
<channel>
  <title>OpenVZ</title>
  <link>https://openvz.livejournal.com/</link>
  <description>OpenVZ - LiveJournal.com</description>
  <lastBuildDate>Mon, 26 Mar 2007 11:40:29 GMT</lastBuildDate>
  <generator>LiveJournal / LiveJournal.com</generator>
  <lj:journal>openvz</lj:journal>
  <lj:journalid>9392309</lj:journalid>
  <lj:journaltype>community</lj:journaltype>
  <image>
    <url>https://l-userpic.livejournal.com/128680075/9392309</url>
    <title>OpenVZ</title>
    <link>https://openvz.livejournal.com/</link>
    <width>100</width>
    <height>100</height>
  </image>

  <item>
  <guid isPermaLink='true'>https://openvz.livejournal.com/14024.html</guid>
  <pubDate>Mon, 26 Mar 2007 11:40:29 GMT</pubDate>
  <title>benchmarks; Xen vs OpenVZ</title>
  <author>k001</author>
  <link>https://openvz.livejournal.com/14024.html</link>
  <description>&lt;p&gt;There is a somewhat interesting &lt;a href=&quot;http://weblog.infoworld.com/virtualization/archives/2007/03/xensource_versu.html&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;article at the Infoworld blog, discussing the VMware vs. Xen and Xen vs. VMware benchmarks&lt;/a&gt;. It appears VMware did a not-quite-good job comparing their ESX to Xen, so Xen came back and presented another comparison, where it is either on par or a bit better than ESX.&lt;/p&gt;

&lt;p&gt;From my experience working as Virtuozzo QA team leader (a few years ago) doing all sorts of performance and stress tests for Virtuozzo kernel, I know that there are very many factors influencing the results. Consider this: if you happen to run your test while cron is running daily jobs like slocate&apos;s update, log rotation routines etc., your performance could be 10 to 50 per cent slower. This was a very simple and obvious example -- just disable cron daemon before you do your testing. A trickier example is when networking performance increase by 10 to 15% if you bound a NIC interrupt to a single CPU on an two or four-way SMP box.&lt;/p&gt;

&lt;p&gt;So, my suggestion is to take those benchmarks and comparisons with a grain of salt. Better yet, do your own comparison using your hardware and your workloads -- and make sure you understand all the results. So if something is slow -- find out why. If something is faster than it should be -- find out why, find out what you did wrong. Perhaps this part -- results analysis -- is the most complex part in the performance testing field.&lt;/p&gt;

&lt;p&gt;Having said that, I&apos;d like to point out a Xen vs. OpenVZ comparison, done by a German student Björn Gross-Hohnacker who I met at last year&apos;s LinuxWorld Cologne. Björn graciously allowed us to publish his results, so we have translated part of it into English.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;http://download.openvz.org/contrib/doc/xen-vs-openvz/Diplomarbeit%20Servervirtualisierung.pdf&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;Full paper (in German, 103 pages, 932K PDF)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;http://download.openvz.org/contrib/doc/xen-vs-openvz/Diplomarbeit%20Servervirtualisierung%20English%20(part).pdf&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;Xen vs. OpenVZ benchmarks (in English, 17 pages, 445К PDF)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Here is the bottom line summary: IPC and disk I/O performance is better (or much better) for OpenVZ than Xen, CPU-intensive tasks are about the same for both, networking is a bit better in OpenVZ. Conclusion: for homogeneous (i. e. Linux-only) environments, OpenVZ is way better -- as it was designed to be.&lt;/p&gt;

&lt;p&gt;You &lt;b&gt;are&lt;/b&gt; taking this with a grain of salt, aren&apos;t you? ;)&lt;/p&gt;

&lt;b&gt;Update:&lt;/b&gt; comments disabled due to spam</description>
  <category>performance</category>
  <category>vmware</category>
  <category>openvz</category>
  <category>comparison</category>
  <category>xen</category>
  <category>benchmark</category>
  <lj:security>public</lj:security>
  <lj:poster>k001</lj:poster>
  <lj:posterid>990679</lj:posterid>
  <lj:reply-count>13</lj:reply-count>
  </item>
</channel>
</rss>
