VMware Communities: High Host Memory Usage on some VMs

VMware Communities: High Host Memory Usage on some VMs


Remember that host memory and guest memory are different. When a guest allocates memory , the host takes memory and gives it to the vm. As a guest uses and stops using that memory, it does not mark the memory as "no longer in use", so ESX can not reclaim it, so by default, the host memory usage will steadily go higher and higher, up to the max allocated to a vm, plus some overhead. This will remain that way until the vm is restarted, or if there is memory contention in the ESX host, at which time ballooning will kick in to reclaim some memory.


-KjB
VMware vExpert

Negotiation

never name the price, always ask!! else you are always in the weeker position -- always


" NZ realestate investors secrets 'page 137' "

money

wealth
gift
freedom
comftable
lifestyle
earned
created
success
educate

IBM developerWorks : Blogs : An exchange and discussion of Storage Virtualization

IBM developerWorks : Blogs : An exchange and discussion of Storage Virtualization: "When to use SEV is a good question. It really depends on the application, and how it behaves. Many open system applications typically run at no more than 50% capacity utilisation. Thats a lot of spindles and space being wasted. With SEV you can now specify a base size and let the application grow to the size it needs. Generally again most applications only then grow at a slow and steady rate. Traditional techniques are to provision as large a disk as maybe needed next year, or the year after, now you can really use what you need. Again, it comes down to understanding your needs, your application needs and the corresponding performance requirements of the application and IBM can help you with all aspects of planning, implementing, testing and through into production."