VMware

This Question is Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
4 Replies Last post: Aug 8, 2008 11:16 AM by tmilner  

Memory pressure? posted: Aug 7, 2008 10:05 PM

Click to view tmilner's profile Enthusiast 131 posts since
Oct 19, 2005


At one of the VMworld presentations I heard a discussion regarding when the esx kernel decides to swap. The jist of the talk was that if you sum up virtual machine memory requirements and divide by available esx memory you end up with a value called "memory pressure". Any value less than 1means that there's plenty of memory available for VMs and life is good. Values greater than 1 means that something must be done to continue (swapping, balloon memory, shared memory,etc.)

I loved the talk... til I asked "where do I get this counter?" Silence. Anyone have any ideas?

Tom

Re: Memory pressure?

1. Aug 7, 2008 11:19 PM in response to: tmilner
Click to view drummonds's profile Hot Shot 112 posts since
May 31, 2007

Tom,

I'm pretty sure that such a counter doesn't exist. But it can be easily determined: just check the free memory on the host in either VirtualCenter or esxtop. Just as easily as saying "when the memory pressure approaches 1" one could say "when free memory approaches zero."

Details on memory stats on Memory Performance Analysis and Monitoring. You're specifically looking for the last entry ("free") on the PMEM row of the memory screen in esxtop or mem.heapfree.average in VirtualCenter.

Scott

Re: Memory pressure?

3. Aug 8, 2008 9:58 AM in response to: tmilner
Click to view drummonds's profile Hot Shot 112 posts since
May 31, 2007

I can give you some help there, too. The "how bad are things?" question can best be answered at by checking the swap rate. There's documentation on the esxtop and VirtualCenter counters that detail swap rates at Memory Performance Analysis and Monitoring. There's a good rule of thumb that if your host is swapping, your performance problems are serious.

Unfortunately, what we can't answer via counters is something that this idea of a "memory pressure" counter would fix. Knowing a ratio of needed v. present memory would tell us exactly how much memory needs to be added to the box to correct the problem. As this stand with swapping, the solution is to add a little more and check if swapping has been eliminated. If not, rinse and repeat.

Of course, you could determine exactly how much memory is needed by just adding up the amount of active memory for all VMs. But that's going to require some math on your part. :)

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities