Craig

Consumed memory looks reasonable. Most times when the OS and applications start they allocate a bunch of memory (a.k.a. "consume" it) by setting up buffers, caches, etc. They then may never actually write any data there (i.e. cache never fills, etc.). In this case the VM is 3.9GB allocated to it, the OS + apps have issued memory requests for 3.6GB, and if busily using 1.5GB of that so the proportions make sense i.e. (granted > consumed > active).

There may not be a direct relationship between "Available" in System Information and "Consumed" in VC. Page sharing is going on (ESX looking for pages that can be shared thus reducing the "consumed" value). When I add "Memory Shared" to my graphs it is almost a mirror image of "Memory Consumed" (i.e. if "Memory Shared" is going up then "Memory Consumed" tends to be going down at the same time). If there are no other VMs running on the ESX server then they should be very close.

From a performance perspective memory looks good. The counters you have show the "Memory Balloon" driver is not active, meaning that there is no memory overcommitment putting pressure on this VM to give up memory. You could also add "Memory Swapped" just to verify that ESX is not doing any swapping, however I'm almost 100% certain there is no swapping from looking at Memory Active and Memory Consumed.