The Win10 Pro virtual machine's VMDK was located on the StarWind datastore. The VMDK that the StarWind VSA VM uses to store image files was eager zeroed, but the Win10 Pro VMDK itself was not eager zero'd. I know you're supposed to thick provision eager zero all the VMDK's that the StarWind VM uses ...

So today I updated the network drivers/VIBs within ESXi for the adapter (nmlx5-core) with the most recent ones from Mellanox's website and disabled DRSS/RSS mode as recommended in the release notes for vSphere 6.7. This helped a little bit and I was able to get 20Gb/s with iperf directly from ESXi h...

But doesn't iperf run tests in memory? And if it was going to the RAID5 array, its an all-flash array, so shouldn't it get more than 15Gb/s?

So I'm currently doing some testing with StarWind VSA for a 2-node vSphere setup and am having some issues. Both our servers are equipped with 5x 1.2tb write-intensive SSD's in a RAID5 on a P440ar storage controller, and dual-port 25gb/s HPE/Mellanox 640FLR-SFP28 Ethernet cards directly connected to...