These are old tests now and not necessarily perfect, but they were Xen<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">


and KVM on the same kernel. KVM very early on and not necessarily in<br>
its best light. The Xen dom0/domU kernel was also not the best light<br>
for Xen. The point was to try to compare them on the same kernel. Xen<br>
and KVM on the same kernel has happened in the form of OpenSUSE&#39;s<br>
forward port of the Xen dom0 kernel with KVM that is already in<br>
mainline. The pv_ops kernel is not fully mainline, but is getting<br>
close. Some distros now have Xen dom0 kernels based on the pv_ops<br>
kernel, which could also run KVM.<br>
<br>
I wonder if using things like puppet, the phoronix test suite, etc.<br>
are a simpler way to go? I guess it all depends on how general a<br>
benchmarking tool is needed.<br>
<div class="im"><br>
Thanks,<br>
Todd<br>
</div></blockquote></div><br>Todd, I think there&#39;s more than one way to look at this as well. As Xen becomes more of a product and less of an installable package<br>it will probably have to be profiled as a product. Say benchmark XCP on particular hardware and benchmark RHEL KVM on the same hardware and ESX as well.<br>

It makes sense to benchmark a XEN kernel and a KVM kernel if we have that flexibility but that&#39;s starting to shrink. Another test that I don&#39;t think <br>is THAT important anymore is tesing Xen with and without pvops kernels. There were some rumors going around that the old 2.6.18 kernel was faster<br>

than the new pvops. I was going to put together tests and never got to it. Not that it makes any difference in the future because the old kernel is fast going <br>away.<br><br>What I&#39;d like to have is a standardized test with a way of multiple people uploading it and comparing results so we can run it on as many systems as possible. <br>

Data correlation could then be done on the data. Currently we have one test over here and another over there and the tests never seem to be updated or even <br>run again to verify results. Maybe none of it matters as the hypervisor becomes inconsequential. <br>

<br>I&#39;m going to look at the tests you&#39;ve done as soon as time permits.<br><br clear="all">Grant McWilliams<br><br>Some people, when confronted with a problem, think &quot;I know, I&#39;ll use Windows.&quot; <br>
Now they have two problems.
<br>