Announcement

Collapse
No announcement yet.

The Start Of Some KVM Virtualization Benchmarks

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • The Start Of Some KVM Virtualization Benchmarks

    Phoronix: The Start Of Some KVM Virtualization Benchmarks

    The last time we published any benchmarks using KVM (the Kernel-based Virtual Machine) virtualization was last year when looking at the performance with the Linux 2.6.31 kernel and before that when looking at the Intel Core i7 virtualization performance. However, a new set of Linux virtualization benchmarks are being worked on...

    http://www.phoronix.com/vr.php?view=ODM3NA

  • #2
    have you got an agreement with vmware? Don't they still dissalow all (published) benchmarking in their EULA?

    Comment


    • #3
      What about xen-4.0-testing + jeremy's kernel with blktap2?
      ## VGA ##
      AMD: X1950XTX, HD3870, HD5870
      Intel: GMA45, HD3000 (Core i5 2500K)

      Comment


      • #4
        I'm not a very serious KVM user but my one complaint about it is that compiling is very slow, much more by comparison than anything else. I believe this is a known problem. It has been suggested that setting the virtio storage device to rotational mode on the guest and using the deadline scheduler on the host can help a little but Windows XP doesn't support virtio storage. I think it only gives you a small gain anyway.

        Comment


        • #5
          It would be useful to know exactly how you configured the storage and networking of the VM, as these can obviously have a significant impact on performance. Especially, I believe you get the best disk performance if you use a host LVM volume as the storage for the VM. I can certainly put you in touch with some of the RH virt folks if it would help to make sure you get the optimal KVM configuration.

          Comment


          • #6
            It would be interesting to see KVM tested with and without virtio!
            (http://wiki.libvirt.org/page/Virtio)

            Comment


            • #7
              Make sure KSM is disabled

              Comment


              • #8
                When you're doing the virtualbox testing, it'd be nice to see the results both with and without hardware virt support (seeing as how qemu's equivalent kqemu seems depreciated...).

                I second (or third?) the call for virtio disk/nic testing and comparisions, and the other kernel paravirt options.
                Actually, if testing with a "bleeding edge" kernel or whatever, seeing what kind of difference the new host-side vhost net driver makes would be sweet too.

                Originally posted by lordmozilla View Post
                have you got an agreement with vmware? Don't they still dissalow all (published) benchmarking in their EULA?
                Seriously?

                I wonder if that'd even be enforceable...

                Comment


                • #9
                  Originally posted by vorgusa View Post
                  Make sure KSM is disabled
                  I second that.
                  KSM can have a devastating effect on the performance.
                  Beyond that, using all of host's memory for a VM is a very bad idea, you lose the disk caching on the host side and may even force the host to swap output memory.

                  In short:
                  Upgrade the machine to 6GB (give 4 to the guest).
                  Disable KSM.
                  Graphical test should performance better with -vga std or vmware.

                  - Gilboa
                  oVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q.
                  oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX550 (to-VM).
                  oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM), Dell U2711.
                  Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.

                  Comment


                  • #10
                    Besides an upgrade to 6Gb, I would also suggest to give 50% of host memory to the guest, so that we could compare the virtual systems benchmarks (using 3Gb) with the native execution with 3Gb (an important extra).

                    Michael, were you considering something like this?

                    Comment

                    Working...
                    X