Turn on "Discard" option?

you need to set cache of vdisk to "write back" to have same performance of bare metal, because proxmox set cache to none by default.
write-back is unsafe, the chances of losing data is much higher. This needs to be mentioned before recommending it for performance.
 
Capturing this thread. Does it make sense to have 'Discard' enabled in my environment? 3 node cluster, shared Storage via DellEMC PowerVault. Volumes are created via LVM and qcow2 is used. I'm a bit confused with the thin provisioning requirement. On what level is this?

PowerVault Volume: thin provisioned
Proxmox LVM: thick provisioned
VM QCOW2 disk format: thin provisioned

As my PowerVault Storage are SAS disks, I better not set SSD Emulation? What about using IO threads?
 
Capturing this thread. Does it make sense to have 'Discard' enabled in my environment? 3 node cluster, shared Storage via DellEMC PowerVault. Volumes are created via LVM and qcow2 is used. I'm a bit confused with the thin provisioning requirement. On what level is this?

PowerVault Volume: thin provisioned
Proxmox LVM: thick provisioned
VM QCOW2 disk format: thin provisioned

As my PowerVault Storage are SAS disks, I better not set SSD Emulation? What about using IO threads?
Currently they are no thinprovisioning, so It'll not help for lvm+qcow2 to retreive space. (as the lvm under qcow2 is thick)

But it could reduce the size of you backup as it's cleaning the disk blocks on file deletion.