These parameters are things like CPU model, family & stepping, various CPUID bits, etc. One of the areas that can be improved is for instance including host configuration parameters. This is the reason why engineering is exploring ways of improving it. Note that static overhead memory estimation is calculated fairly conservative and we take a worst-case-scenario in to account. The enabling/disabling of various VMware features (FT, CBRC etc).Several virtual machine configuration parameters like the number vCPUs, amount of vRAM, number of devices, etc.Static overhead memory of a VM depends upon various factors: Once a VM is powered-on, the amount of overhead memory required to keep it running is called dynamic or runtime overhead memory.

When a VM is powered-off, the amount of overhead memory required to power it on is called static overhead memory.I added some bits and pieces where I felt additional details were needed though.ДЇirst of all, what is static overhead and what is dynamic overhead: I found it very useful hence the reason I asked Aashish if it was okay to share it with the world. The question was around what determines the static memory and this is the answer that Aashish provided. Aashish is working on improving the overhead memory estimation calculation so that both HA and DRS can be even more efficient when it comes to placing virtual machines. Coincidentally I spoke with Aashish Parikh from the DRS team on this topic a couple of weeks ago when I was in Palo Alto. We had a discussion internally on static overhead memory.

What is static ram and dynamic ram