At first glance, Proxmox appears to offer substantial improvements over the old setup, with a few important observations:
1) According to Samsung’s official specifications this model is rated for 6800 MB/s sequential read and 2700 MB/s...
For reference, the existing Hyper-V Server deployment (on identical hardware) yields the following results:
C:\> fsutil fsinfo sectorInfo C:
LogicalBytesPerSector : 512
PhysicalBytesPerSectorForAtomicity ...
A minor correction: Using scsi-hd.logical_block_size=4096 had a measurable (negative) impact on sequential write performance.
The remaining results appear to be within statistical tolerance.
I’m evaluating Proxmox for potential use in a professional environment to host Windows VMs. Current production setup runs on Microsoft Hyper-V Server.
Results follow:
1) Using
--scsi0 "$VM_STORAGE:$VM_DISKSIZE,discard=on,iothread=1,ssd=1"...
Out of curiosity, what additional value would this bring compared to the existing --args option?
Also, I’ve been running benchmarks with various logical and physical block sizes, but they seem to have no effect on performance -- only on the...
I'm encountering the same issue today:
# pveam download local debian-13-standard_13.1-2_amd64.tar.zst
downloading http://download.proxmox.com/images/system/debian-13-standard_13.1-2_amd64.tar.zst to...