Hello, I noticed that in Virtual Machines, the performance of reading and writing the disc is much lower than a container or in the node itself. Does anyone know why this occurs, and if there's a way to get better?
VM:
CT:
VM:
CT:
low perforace of the disk on VM
- Thread starter Rogerio Alves Moreira
- Start date
Hello Rogerio,
This happen because of virtualization.
While in Virtual Machines you are emulating the PCI bridge, driver controller and disk drive in containers this is not happening. A virtual machine runs his own kernel while in containers the hernel is shared with the host system.
There are different types of hardware emulation, there are some emulations which presents "real hardware" to the guest operative system and others presents hardware which is clearly emulated as virtio drivers.
Take a look to the documentation in order understand which VM setup is better for your system.
About disk and VMs
pve admin guide
pve wiki
About containers
pve admin guide
This happen because of virtualization.
While in Virtual Machines you are emulating the PCI bridge, driver controller and disk drive in containers this is not happening. A virtual machine runs his own kernel while in containers the hernel is shared with the host system.
There are different types of hardware emulation, there are some emulations which presents "real hardware" to the guest operative system and others presents hardware which is clearly emulated as virtio drivers.
Take a look to the documentation in order understand which VM setup is better for your system.
About disk and VMs
pve admin guide
pve wiki
About containers
pve admin guide
With which type of disk on which storage?
Performance depends also on the underlying hardware and software.
I am sure it the results are going to be different as qcow2 format on dir than raw in LVM.
Take a look to the documentation
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_storage