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] Another disadvantage is that, when running out of real memory, the system is relying on the applications to not use the additional memory despite it being allocated to them. Should a program do so anyway, it or another has to be killed in order to free up memory to prevent the system from freezing. The OOM Killer is what performs this task.

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

edit

References

edit
  1. ^ Portnoy, Matthew (2012). Virtualization Essentials. John Wiley & Sons. pp. 60. ISBN 978-1118240175.
  2. ^ Siebert, Eric (2009). VMware VI3 Implementation and Administration. Prentice Hall Professional. pp. 166. ISBN 978-0137008599.
  3. ^ "VMware vs. Microsoft: Why Memory Overcommitment is Useful in Production and Why Microsoft Denies it". Archived from the original on 5 March 2016. Retrieved 22 April 2015.{{cite web}}: CS1 maint: bot: original URL status unknown (link)
  4. ^ Santosa, Mulyadi. "When Linux Runs Out of Memory". O'Reilly Media. Retrieved 22 April 2015.


Stub icon

This computer science article is a stub. You can help Wikipedia by adding missing information.

📚 Artikel Terkait di Wikipedia

Memory ballooning

Sons. ISBN 9781118828335. "Balloon Driver". Driver Red Hat Product Documentation. Retrieved 2024-05-08. Memory overcommitment Thin provisioning v t e

Memory management (operating systems)

region terminates. Base and bounds Memory overcommitment Memory protection Region-based memory management x86 memory segmentation Known as TSO regions

Memory paging

swap death. Swap death can happen due to incorrectly configured memory overcommitment. The original description of the "swapping to death" problem relates

Virtual machine

technology evolves virtual memory for purposes of virtualization, new systems of memory overcommitment may be applied to manage memory sharing among multiple

Memory virtualization

retrieve data. Management software and the technologies of memory overcommitment manage shared memory, data insertion, eviction and provisioning policies, data

System virtual machine

technology evolves virtual memory for purposes of virtualization, new systems of memory overcommitment may be applied to manage memory sharing among multiple

Bin packing problem

the capacity. Therefore, the cloud manager may gain a lot by slight overcommitment. This induces a variant of bin packing with chance constraints: the

Occupational stress

appreciation and fair treatment. Another facet of the model is that overcommitment to the job can fuel imbalance. The person–environment fit model underlines