Deep Dive: The Storage Pool in Storage Spaces Direct

Hi Cosmos and thank you for this extremely useful explanation.

I am hereby assuming (please correct me if I'm wrong) that you can manually "regulate" slabs size by tweaking the "New-VirtualDisk -AllocationUnitSize" parameter.

If my assumption is correct then why creating a New-VirtualDisk via PowerShell gives me a 1GB slab vs 256MB from the GUI?

Also, given the AllocationUnit-term has already been taken (whenever you mention Allocation Unit, everyone automatically thinks at the cluster size), wouldn't it have been better to call the New-VirtualDisk parameter "-SlabSize" ?

Please clarify for everyone's benefit and feel free to share (any) performance consequences between the two values (1GBvs256MB Slabs).

Thanks,

Andrea.