I found an odd situation where ProxMox swapps allmost all VMs out to disk while copying some files. And i can not find an explanation.
In detail: I copy some files(about 8G) from within a VM (Debian, ISCSI-Disk via VIRTIO ) via Samba-Share to an external machine. So it is only reading from disk and some transmitting I would assume.
Transmission is very slow on the one hand (3MB/s) and I/O-delay goes up to 70%.
On the other side allmost all memory of running VMs is being stored to the swap space. This leads to a very poor performance on all VMs afterwards.
I dont understand why this happens while I am only reading some files...
I try to prevent that with swappyness = 0 but no effect.
How would Proxmox behave without swapspace at all? I have no testing machine at the moment, only production. Has anybody tested that?
Regards Holgi
In detail: I copy some files(about 8G) from within a VM (Debian, ISCSI-Disk via VIRTIO ) via Samba-Share to an external machine. So it is only reading from disk and some transmitting I would assume.
Transmission is very slow on the one hand (3MB/s) and I/O-delay goes up to 70%.
On the other side allmost all memory of running VMs is being stored to the swap space. This leads to a very poor performance on all VMs afterwards.
I dont understand why this happens while I am only reading some files...
I try to prevent that with swappyness = 0 but no effect.
How would Proxmox behave without swapspace at all? I have no testing machine at the moment, only production. Has anybody tested that?
Regards Holgi