Everything About ___
Live briefing

Everything about Memory overcommitment

Memory overcommitment is a concept in computing that covers the assignment of more memory to virtual computing devices than the physical machine they are hosted, or running on, actually has. This is possible because virtual machines 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. 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. 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. Wikipedia →

đź§­ Start here: a 6-step reading path

  1. Read the overview: Memory overcommitmentA 5-minute orientation
  2. Read the landmark paper: Proactively Breaking Large Pages to Improve Memory Overcommitment Performance in VMware ESXiCited 0 times
  3. Go sideways: Comparison of platform virtualization softwareA closely related topic
  4. Go sideways: Memory pagingA closely related topic

đź“– Definitions

No dictionary entry for this exact phrase.

🗂️ The subject at a glance

No outline available.

🏆 Landmark papers (most cited)

📚 Books worth reading

Open Library didn't respond; try again in a moment.

đź”— Related topics