tdean wrote: » I dont think our terminal server vm's are performing as well as they should. I was on the vmware boards and they claim you should almost never allocate more than 512mb ram for a windows server vm. i looked at ours and they have over 2.4Gb allocated. at some point, i will be upgrading this from ESX3.x to ESXi 4.1. when i do that, should i change the ram settings?
certhelp wrote: » 512mb RAM? Even with 1024MB/1GB RAM, Server 2008 crawls. Does Your host on which the VM is hosted have enough RAM? It should have enough RAM for all the guests + the host. I don't think 512MB is max RAM is a valid advice.
SteveO86 wrote: » Yea.. 512 MB for a server.. That's..not....a solution... but hey one of those guys are a vExpert... So maybe it's me. Are you sure the host only 2.5 GB of RAM, I would definitely get that upgraded.
Devilsbane wrote: » I like to do 1GB if I can, but 512MB is normal and I have even ran on 256 before. At least with my machines, I'm really not doing anything on them. They usually just sit there idle until I go test something, so there really isn't a large demand for performance. These are also running xp/2003 and not a memory hog like Vista.
Essendon wrote: » I think he's referring to his prod environment.
MentholMoose wrote: » The thread you linked is ancient so don't pay attention to it. The advice was OK at that time since RAM was more expensive and people were more conservative with allocating it to VMs. Also at least one reply was clearly recommending 512MB as a starting point... generally you give VMs fewer resources and only allocate more if you have a reason to. If you notice in that thread, the OP allocated 2GB RAM to a VM when the host only had 2.5GB of physical RAM, which may not leave enough for the host (let alone other VMs). If you are having performance problems in a VM, check the resource utilization for that VM. You can do that by just treating it as a physical server and using tools like Task Manager or Process Explorer inside the VM. In your screenshot, it looks like one of the VMs is alerting for high CPU usage and/or high RAM utilization, so look into what is causing that. Also, what type of datastore are these VMs stored on (local, iSCSI, FC, NFS)?
MentholMoose wrote: » How many cores do the hosts have? If you can schedule a short maintenance window, you can try reducing the vCPU count for one of the problem VMs to see if it resolves the issue. The procedure is simply 1) shutdown VM, 2) edit vCPU count in VM Properties, and 3) boot VM.