Hyper-V vs. Virtuozzo




Our advice is - If your budget allows always go with a Dedicated Cloud instead of a VPS or at least go with a hypervisor based virtaulization!

Compare VPS plans

Compare Dedicated Cloud plans

  1. VPS virtualization based on a container concept provided by OpenVZ/Virtuozzo is NOT the same as hypervisor virtualization provided by MS Hyper-V and as such can NOT replace a Dedicated server and should not be used instead of a Dedicated server

  2. If you need a lot of CPU, memory, and I/O resources VPS based on a container concept will NOT work for you

  3. If your application requires a lot of heavy I/O such as Database, Streaming, lots of web traffic - you should go with a Dedicated Cloud server or virtualization provided through a hypervisor technology such as Hyper-V. The container based VPS bottleneck is I/O resources which at some point become a major bottleneck and you will be forced to upgrade to a Dedicated server

  4. VPS based on OpenVZ/Virtuozzo should NOT be used for mission critical applications! If the uptime and performance are critical factor than a Dedicated server is a MUST have and here is why:
    • NOT all VPS resources in a container are reserved ONLY for your VPS. For example I/O sharing, network port sharing, and "burstable" memory sharing can impact your site and account performance. On the other side a hypervisor virtualization provides dedicated or guaranteed system resources for your VPS
    • The container based VPS performance and stability maybe impacted if the actual hardware node hosting your VPS becomes unstable which can happen in certain cases if another VPS is abusing the shared I/O resources of the node or if there is a problem with the node (for example operating system crash). Such problems are not present or at least are much better isolated in a hypervisor VPS implementation
    • The Linux/Windows VPS kernel in a container based platform can not be updated. You can not update on your own your VPS operating system and can not perform any system related updates. This is not the case with a hypervisor virtualization
    • Low level drivers, which requires kernel changes/updates cannot be installed in the container based virtualization. For example some VPN software won't work in container environments. All of these are possible with a hypervisor virtualization
    • You can NOT use swap in the container based VPS platform, which means that your VPS will be limited to the actual VPS memory. With a hypervisor virtualization your VPS can use a swap space
    • You cannot perform custom OS updates as all updates have to be first verified by the VPS software vendor. With a hypervisor VPS you can perform any OS updates