Let’s look at an example of what happens when Hyper-V machine memory is over-committed and the Dynamic Memory Balancer attempts to adjust to that condition. The scenario begins with five Windows guest machines running with the following dynamic memory settings: Minimum Maximum WIN81TEST1 2 GB 6 GB WIN81TEST2 2 GB 6 GB WIN81TEST3 512 MB 6 GB WIN81TEST4 512 MB 6 GB WIN81TEST5 512 MB 8 GB In the scenario, four of the five guest machines are doing actual work. Only guest machine 5 is active, as illustrated in the screen shot of the Hyper-V Manager console, shown in Figure 17. The Hyper-V Host used in the test contains 12 GB of RAM. The remaining guest machines are idle initially, which allows Hyper-V to reduce the amount of machine memory allocated to guests 3-4 to near their minimum values, using the ballooning technique we discussed. Figure 17. The Hyper-V...
A blog devoted to Windows performance, application responsiveness and scalability, software performance engineering (SPE), and related topics in computer performance.