The results seem quite low indeed. Qemu itself is able to reach 200~300k iops with 1 core. (I'm working to add support for mutiple iothread to increase the performance up to 600kiops by disk, but you are far from reaching the current cpu limit)...
Hi,thanks for the report. I have send patch to the mailing recently to improve the performance of secure erase, it's not yet commited. But I didn't notice this bug with volume activation. I'll look at it next week. (and I'll forward it the dev...
Hi @dchalon , welcome to the forum.
I believe you will need to clone that new VM as full clone. There is no unlink operation.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
never tried it but :
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/chap-kvm_guest_timing_management
To enable the PHC device, do the following on the guest OS:
Set...
It's quite possible that your are cpu limited, as currently vm can only use 1 core for 1 virtual disk.
Multiple threading (with multiple iothread by disk), should be available soon, I have already send patch to the proxmox dev mailing list.
more than one OSE per nvme will not help. non PLP are really like 500iops 4k write vs 20000iops for plp drive.
At minimum, use cache=writeback, it should help to avoid small write when possible (merging small adjacent writes to big write)