JonesytheGreat wrote:
One example I have right now is for an exchange server. The server has 24GB of memory assigned to it, but vmware shows the active memory is only around 2GB. I should be able to give this server 3-4GB of memory and it should be happy. I don't know why the memory explinations in vmware have to be so difficult. Fixing the descriptions for "consumed", overhead consumption, private, and active" would be of great benefit.
Thanks,
Matt
Depending on the version of Exchange you are running (and the role that is installed), you need to let it have some extra room for cache. During peak times, or during unexpected periods of multiple large messages being sent, memory pressure can cause mail to queue up or even bounce. There are applications that you really should refer back to the vendor (in this case, Microsoft) to get an idea for the minimum recommended specs for that server role. 24GB may be overkill, but 4GB might be cutting it too close.