The memory consumed model is the default resource capacity model. It demonstrates the consumption of memory from a guest point of view, in contrast to the memory demand model, which is based on active memory usage from a vSphere perspective. The memory consumed model becomes relevant when applications such as Microsoft SQL Server claim all available memory at the virtual machine level, and thus report higher memory usage than the active memory used.

If an environment is relatively conservative in respect to capacity planning without memory over allocation, then turn on the allocated, consumed, and demand memory models. This action enables you to see how much memory you can safely get back if you relax your capacity planning policy. vRealize Operations helps ensure that you never run out or use the consumed and demand memory models for more aggressive workload deployment on hosts.

To stop vRealize Operations from reporting that your thin-provisioned storage is out of capacity, turn off the disk allocated model and only leave the demand mode active.