Performance Testing Hypervisors with AL-Go
dasite.quattrofan.de
Contents Why? What? Where? The Tests The Test VM Apache Cloudstack Hyper-V Bare-Metal XCP-ng Proxmox / KVM Results / Comparison Charts Conclusion Surprises Foreword I am fully aware, that as soon as you post something on the Internet, no matter what, someone will tell you and prove that you are wrong. I am always happy to get constructive feedback to improve things, though. But it is unlikely that I will run this series of tests again soon, because including writing this article and trying to figure out how Hugo works, that whole adventure took 3 days off my 1 week holiday ;-)

I spent a few days comparing various Hypervisors under the same workload and on the same hardware. This is a very specific workload and results might be different when testing oher workloads.

I wanted to share it here, because many of us run very modest Hardware and getting the most out of it is probably something others are interested in, too. I wanted to share it also because maybe someone finds a flaw in the configurations I ran, which might boost things up.

If you do not want to go to the post / read all of that, the very quick summary is, that XCP-ng was the quickest and KVM the slowest. There is also a summary at the bottom of the post with some graphs if that interests you. For everyone else who reads the whole post, I hope it gives some useful insights for your self-hosting endeavours.

  • 0x0@programming.devEnglish
    16·
    2 days ago

    Not being an expert it seems as though your setup is windows-centric, whereas KVM tends to shine on linux.

    • buedi@feddit.orgOPEnglish
      11·
      2 days ago

      Yes, it is Windows centric because that is where the workload is based on I need to run. It would be cool to see a similar comparison with a workload under Linux that puts strain on CPU, Memory and Disk.