Worst Case Allocation (Shared Memory) Confusion

[shimmyt]

I have a VM that has 24GB of memory in its own resource pool that is showing a "Worst Case Allocation" of 24.40 GB. It currently states that 1.32GB is being shared even though there is a reserve of 24GB set. According to the documentation the Worst Case Allocation is something I set through shares and reservations. What I don't understand is how I got to 24.4GB and why 1.27GB of memory is being shared. The resource pool is currently set to:

Shares: Normal

Reservateion: 24988MB with expandable reservation checked

Limit: Unlimited

And on the VM:

Shares: Normal

Reservation: 24576 (I set that)

Limit: Unlimited

Am I missing something here? Or is this default behavior?

[beth22]

Shared is the total amount of memory that is being shared by using TPS.

Worst Case Allocation is the total amount of memory of your VM when all VMs in the cluster consume their full amount of allocated resources or when overcommitment happens this is what amount of memory that VM can get. It might includes memory overhead that's why it is larger than configured memory.