Memory overcommitment
Memory overcommitment is a concept in computing that covers the assignment of more memory to virtual computing devices (or processes) than the physical machine they are hosted, or running on, actually has. This is possible because virtual machines (or processes) do not necessarily use as much memory at any one point as they are assigned, creating a buffer. If four virtual machines each have 1 GB of memory on a physical machine with 4 GB of memory, but those virtual machines are only using 500 MB, it is possible to create additional virtual machines that take advantage of the 500 MB each existing machine is leaving free.[1] Memory swapping is then used to handle spikes in memory usage. The disadvantage of this approach is that memory swap files are slower to read from than 'actual' memory, which can lead to performance drops.[2] While memory overcommitment is usually talked about in the context of virtualization, it is actually a generalised concept; Windows NT contained overcommitment features, as do most modern generalised operating systems,[3] including the Linux kernel.[4]
See also
References
- ↑ Portnoy, Matthew (2012). Virtualization Essentials. John Wiley & Sons. pp. 60. ISBN 978-1118240175. https://archive.org/details/virtualizationes00port.
- ↑ Siebert, Eric (2009). VMware VI3 Implementation and Administration. Prentice Hall Professional. pp. 166. ISBN 978-0137008599. https://archive.org/details/whatsupamericani00mcpa_044.
- ↑ "VMware vs. Microsoft: Why Memory Overcommitment is Useful in Production and Why Microsoft Denies it". https://www.sepago.com/blog/2008/09/25/vmware-vs-microsoft-why-memory-overcommitment-is-useful-in-production-and-why.
- ↑ Santosa, Mulyadi. "When Linux Runs Out of Memory". O'Reilly Media. https://blog.csdn.net/maimang1001/article/details/29630477. Retrieved 22 April 2015.
 |  |
