官术网_书友最值得收藏!

How to do it…

To spot the average Active Memory, you should check both the VM level and host level. To monitor at the VM level, perform the following steps:

  1. Open up vSphere Web Client.
  2. Log in to your vCenter Server.
  3. On the Home screen, select VMs and Templates.
  4. Choose the VM where you want to monitor Active Memory.
  1. Go to the Monitor tab, then the Performance tab, and then click on Advanced.
  2. Change the view to Memory, then click on Chart Options.
  3. Select the Active, Balloon memory, Consumed, and Granted counters from the list and click on OK to continue. Active is the counter that usually estimates how much the VM would actually need.

One of the biggest myths is that when a host is low on memory, performance problems are likely or that the VM needs more memory than it has installed because you're looking at a Granted or Consumed type of counter instead of the Active-type counter.

The following is a sample screenshot that you see once you select the Active counter to monitor memory performance:

In the preceding example, you can see that Memhog-1 is using close to 6.4 gigabytes of memory, which means the Active Memory is 6.4 gigabytes, whereas the granted memory for this VM is 16 gigabytes.

If you want to monitor this counter at the ESXi host level, perform the following steps:

  1. Open up vSphere Web Client.
  2. Log in to your vCenter Server.
  3. On the Home screen, select Hosts and Clusters.
  4. Choose the ESXi host where you want to monitor the Active Memory.
  5. Go to the Monitor tab, then the Performance tab, and then click on Advanced.
  6. Change the view to Memory, then click on Chart Options.
  7. Select the Active, Balloon memory, Consumed, and Granted counters from the list and click on OK to continue.

The following is a sample screenshot that you see once you select the Active counter to monitor memory performance:

In this example, you can see that the ESXi host is using 6811516 kilobytes (6.49GB) of Active Memory.

You may notice the Shared common counter here. This is a measure of savings due to TPS. Having TPS run does not have any downside and does not provide any reason to monitor it either. You could get into the most shared pages being zeroed pages, and the VDI is more likely to share the memory if all the guest operating systems are the same. TPS doesn't work with large pages, which are standard now until you hit a threshold, where large pages are broken down. Then, TPS is started.

Now, to monitor Swapped, Swap in, and Swap out, follow the Monitoring host swapping activity recipe.

主站蜘蛛池模板: 合江县| 双流县| 土默特右旗| 台北市| 襄樊市| 深泽县| 黑水县| 乌审旗| 武威市| 敖汉旗| 芦溪县| 锡林郭勒盟| 麻江县| 闵行区| 庆阳市| 蒙阴县| 余庆县| 通河县| 慈溪市| 烟台市| 长岛县| 锡林浩特市| 罗源县| 阿拉善左旗| 浑源县| 新和县| 基隆市| 富裕县| 龙游县| 镶黄旗| 抚远县| 阿尔山市| 湾仔区| 昭通市| 三亚市| 巢湖市| 尚志市| 怀安县| 临夏市| 错那县| 南乐县|