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

What counters not to use

A lot of the time, we assume that some very popular counters would be better to monitor memory performance. However, many times, it leads to something else. This means that these are not an indication of a memory performance issue. If this counter is combined with something else, then it may indicate performance degradation.

In this aspect, don't use two of the most popular counters just to understand whether the memory is under pressure or not:

  • Mem.consumed (Consumed Memory)
  • Mem.vmmemctl (ballooned memory)

Let me show you what they essentially indicate.

The Mem.consumed counter is the amount of memory consumed by one or all VMs. This is calculated as memory granted minus memory saved by sharing. Now the question is why we should not use this. The reason is that memory allocation will vary dynamically based on the VM's entitlement. It is important that a VM should get whatever it actually demands.

Similarly, Mem.vmmemctl is the amount of ballooned memory. This does not indicate a performance problem as well. However, when it gets combined with host swapping, then it indicates a performance problem.

主站蜘蛛池模板: 定陶县| 兴城市| 尉犁县| 开原市| 吉林省| 米林县| 湘潭市| 龙江县| 任丘市| 曲松县| 兴安县| 茂名市| 六安市| 孝义市| 南华县| 惠东县| 巨鹿县| 仁布县| 亳州市| 察隅县| 油尖旺区| 波密县| 光山县| 仙桃市| 河津市| 沐川县| 邳州市| 肇庆市| 弥渡县| 福泉市| 且末县| 呼图壁县| 无极县| 灵璧县| 汉沽区| 调兵山市| 玉田县| 富蕴县| 花莲市| 股票| 秦安县|