If you have been reading more on sizing your vShpere Clusters with vSAN storage, I am sure you would have factored all the sizing aspects from Compute Perspective (CPU and Mem overcommitment ratios, HA Admission Control etc) and Storage Perspective (Disk Groups, No of Disks, FTT etc)
One of the common questions I get from the customers is Mem overhead on ESXi hosts which are a part of vSAN enabled cluster.
If you have come across Hardware Requirements for vSAN page, you would have observed Memory Requirements depends on number of diskgroups and number of devices which are managed by an ESXi host
- BaseConsumption: is the fixed amount of memory consumed by vSAN per ESXi host.
- NumDiskGroups: is the number of disk groups in the host, this value should range from 1 to 5.
- DiskGroupBaseConsumption: is the fixed amount of memory allocated to each individual disk group in the host. This is mainly used to allocate resources used to support inflight operations on a per disk group level.
- SSDMemOverheadPerGB: is the amount of memory allocated per GB of SSD.
- SSDSize: is the size of the SSD disk in GB.
- NumCapacityDisks: is the number of capacity disks in the host (across all the diskgroups).
- CapacityDiskBaseConsumption: is the amount of memory allocated per capacity disk.
Note: The size of the SSD for all flash is capped at 600GB, and thus using SSDs larger than 600 GB will not consume additional memory.
- BaseConsumption = 5426 MB
- DiskGroupBaseConsumption = 636 MB
- SSDMemOverheadPerGB (hydrid) = 8 MB
- SSDMemOverheadPerGB (allflash) = 14 MB
- CapacityDiskBaseConsumption= 70 MB