Can we call Automatic Striping a “secret feature”? Yup: there’s nothing about it in official documentation. Why? WE DO NOT KNOW! Let’s just see whether we can get any performance boost with Automatic Striping enabled.
So while we were testing VMware vSAN on a 2-node cluster powered with NVMes, the Russian bear slammed in screaming (imagine typical Russian mafia accent) “Dnacv, hold my vodka and give me two
balalaikas servers and I show you how to scale from mother Russia to America”. We thought we don’t wanna mess with drunken bears so here we are. Testing StarWind Virtual SAN for Hyper-V. Yes, there is a version for Linux, (seems that these guys just scale their solution instead of performance?) on a two-node VMware ESXi cluster powered with NVMe drives. Wait what?! VSAN for Hyper-V on top of ESXi? Yes, we have two ESXi hosts with one StarWind VM per each and the VMs are working on top of Windows Server 2016, providing the highly available storage (NTFS, it’s Windows baby) further as a VMFS datastore to ESXi…This is madness…NO! THIS IS STARWIND!!
Pretrial detention due to possible relapse
Measure the 4-node VMware vSAN hyperconverged cluster scalability using vSAN datastore comprised out of 8 Intel SSD DC P370 drives. For this goal, we’ll keep increasing the vSAN datastore load by increasing the VMs number till we reach the saturation point where performance growth stops or till we hit the 12 VMs limit.
Concerns about performance and scalability, but the patient claims that everything is alright
Analyzing patient’s health status LEARN MORE “Another Day – Another Patient: Four-Node VMware vSAN Cluster Performance Report”