The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
Sure. We run IOmeter from the SW VM to get a base. Then we share out that SSD, and run it from a guest from the same machine.nohope wrote:May I ask how did you benchmark the physical storage? As far as I know, it is a bit complicated to simulate writes and reads directly on SSD drive. I think it’s just a matter of inbuilt cache which we cannot go around in doing so.
dwright1542 wrote:That's a good link, thanks. I'm relying right now on the SW guys to nail this down. I feel as that may be squeezing the final IOPS out of the system. I'm only getting 20% of the native IOPS, so there must be something HUGE bottlenecking the system.
-D
This is affecting the native SW Ramdisk as well. Is that the same issue? I'll pass this info along to Oles who's been assisting.anton (staff) wrote:Here's a whole story:
1) Microsoft storage stack is a very old code, it was written and designed when underlying storage was slow. As a result Microsoft isn't going to deliver all possible IOPS from the single very fast NVMe card. There are a couple of workarounds:
a) Disable I/O scheduler. There's going to be less context switches and I/O will be synchronous instead of async.
HKLM\SYSTEM\CurrentControlSet\Control\StorVSP\IOBalance\Enabled:0
So measure performance on NVMe-mapped disk BEFORE and AFTER applying this key (make sure you don't forget to reboot). It's possible to get 30-40% IOPS depending on your configuration (NVMe type, amount of CPU cores and their utilization)
b) Split your card into many logical volumes. Microsoft keeps one I/O queue per volume so when you'll have more volumes you'll have more queues and they will be served by CPU cores more effectively.
2) StarWind is also a very old code so we have issues with delivering high IOPs from one namespace. Increasing number of namespaces help (just like with MSFT n 1b). So get more LUNs with StarWind (w'ell hide them behind vVols for VMware so that's not an issue, Hyper-V will have SMB3 and VHDX files).
Combine 1a and 2 or 1b and 2 (but not both 1a and 1b !!!) and you'll get 100-250K IOPS from a single properly mapped StarWind-managed LUN. StarWind staff should help you with it
kevrags wrote:I'd like to bump this to see if there has been any progress on this.
Thank you,
Kevin