My recent series of blog articles have discussed ESX memory management the the performance specter of host swapping. My last article attempts to correct the misconception that VMware recommends against over-commit memory. In that article I suggested that memory over-commit is requirement in optimizing memory utilization. Today I want to provide a specific example to show why this is true. I am have also included tips for identifying host swapping in your environments.
Understanding the Bottleneck
Let me show the value of over-commit and danger of swapping by way of an example. I will choose the following typical values to demonstrate my point:
To learn more and to read the entire article at its source, please refer to the following page, Optimizing Memory Utilization- Pivot Point - vpivot.com
Article Tags