Performance Overview
Scores based on quantifiable specification values (1-10 scale)
Detailed Specifications
| Specification | VMware vSAN (ESA) VMware | VMware vSAN Max VMware |
|---|---|---|
| Key Metrics | ||
| Architecture | Hyperconverged (compute + storage on same hosts) | Disaggregated (dedicated storage cluster serving external vSphere clusters) |
| Maximum cluster capacity | 8.5 PB | 8.6 PB |
| Maximum nodes per cluster | 64 | 24 data nodes |
| Peak performance | Up to 10.6× OSA on 32K mixed workloads | 3.6 million+ IOPS per cluster |
| Minimum cluster size | 2 nodes (ROBO) / 3 nodes standard | 4 storage hosts (~80 TB raw) |
| Management plane | vCenter (native) | vCenter (native) |
| Compute & Storage Scaling | ||
| Scaling model | Scale compute and storage together (linked) | Scale compute and storage independently |
| Workloads per host | 500+ VMs per host | Storage-only nodes — no VM workloads |
| Compute clusters served | Storage local to compute cluster | Any number of vSphere compute clusters from one storage cluster |
| Capacity per node | -- | Up to 360 TiB per data node |
| Use of compute resources for storage | Shares CPU/RAM with VM workloads | Dedicated to storage — no contention with VMs |
| Storage Architecture | ||
| Storage tiers | Single NVMe tier | Single NVMe tier |
| Data efficiency | RAID-6 erasure coding with RAID-1 write performance | RAID-6 erasure coding with enhanced compression |
| Usable capacity gain vs OSA | Up to 70% more usable capacity | -- |
| Foundation | vSAN 8 Express Storage Architecture | Built on vSAN ESA |
| Snapshots | High-performance ESA snapshots | High-performance ESA snapshots |
| Deployment & Licensing | ||
| Licence model | Included in VMware Cloud Foundation / vSphere Foundation entitlements (per core) | Separate vSAN Max licence (per TiB) |
| Hardware compatibility | vSAN ESA Ready Nodes (strict HCL) | vSAN Max Ready Nodes (strict HCL) |
| Network requirement | 25 GbE recommended for ESA | 100 GbE recommended for storage cluster fabric |
| Cost positioning | Up to 40% lower hardware/software cost for business-critical DBs vs OSA | Targets large-scale capacity workloads where compute:storage ratio is unbalanced |
| Management & Operations | ||
| Management console | vCenter | vCenter |
| Separate storage admin team needed | No | No — same vSphere skillset |
| Skyline Health / vSAN monitoring | Yes | Yes |
| Stretched cluster support | Yes | Yes |
| Data-in-transit & at-rest encryption | Yes | Yes |
Expert Analysis
The decision between vSAN ESA and vSAN Max is not really about which is faster or more modern — both share the same underlying Express Storage Architecture, single NVMe tier, RAID-6 efficiency and vCenter management model. The real question is whether your compute-to-storage ratio justifies keeping them coupled. vSAN ESA is classic HCI: every node contributes CPU, RAM and storage, and the cluster scales as one unit up to 64 nodes and 8.5 PB. vSAN Max breaks that link, letting a 4–24 node storage cluster serve capacity to any number of external vSphere compute clusters, which is the right answer when your data is growing faster than your compute needs (or vice versa).
vSAN ESA is the better fit for the majority of UK mid-market and enterprise deployments — VDI estates, mixed virtualised workloads, branch and ROBO sites, and consolidated business-critical databases where VMware's own figures show up to 40% hardware/software cost reduction versus the older OSA design. Operationally it is the simpler of the two: one cluster, one licence entitlement bundled with vSphere/VCF, 25 GbE networking is sufficient, and there is no separate storage fabric to design. The trade-off is that you cannot grow capacity without also buying compute licences and host hardware you may not need.
vSAN Max earns its place where that trade-off bites — large SQL or Oracle estates, analytics and AI/ML data lakes, container persistent volumes at scale, or any environment where a handful of compute-heavy clusters need to share a single large pool of fast block storage. It does, however, demand a 100 GbE storage fabric, a separate per-TiB licence on top of vSphere, and careful attention to the storage Ready Node HCL. For organisations that have historically run a traditional SAN alongside vSphere, vSAN Max is the more natural migration target than collapsing everything into HCI.
In short: pick vSAN ESA unless you have a concrete reason to disaggregate. Pick vSAN Max when storage growth, multi-cluster consumption, or workload density makes coupled scaling genuinely wasteful — and budget for the 100 GbE fabric and additional licensing it requires.
Ready to proceed?
Want to compare different products or add more to this comparison?
Open Interactive Comparison Tool →