Hey all,
Read through comments on the community and read some of VMWare's docs but I'm still a bit confused on sizing our environment. Currently we have 7 Dell 2950 (2 socket, 2 cores) /w 16GB on a FC Clarion SAN memory getting somewhere between 12-16 VM's per server. Using the very reserved numbers of 6 vCPUs per core (I've read that some are getting 8-10 per core), I should be getting 2 sockets X 2 cores X 6 vCPU's per Core = ~24 light/moderate loaded VM's. Unfortunately I'm not getting quite that performance on my ESX servers. The boxes are mostly Windows 2003 R2 Standard /w SP2 (web servers, file servers, print servers, and some light application servers). Looking through Virtual Center, I'm seeing the hosts at about 60-70% utilization for memory. I use three Resource Pools (not limited to the resources of the Cluster) to break up resources of my cluster. The pools are:
High Pool with 6 machines having a 512 MB reservation and 650 Mhz CPU reservation
Medium Pool with 10 machines having 256 MB reservation and no CPU reservation
Low Pool with all other machines having no reservations (Memory or CPU)
Am I doing something wrong with my configs. All VM's are freshly built on VMWare and have been tweaked (no graphical features, screen saver, unecessary services, etc.). The only thing I can think of is that the VM's are configured with 1024-2048 MB of memory. Could this be the issue? Should I drop the memory allocated in the VMX file for the Low Pool VM's to ~256-384 MB? Virtual Center shows most them using 400-900 MB of memory usage so I'm not to sure I want to drop them to ~256-384 MB due to lack of memory (or is that where the VMWare memory sharing piece comes into play?).
To add to all this, we're looking to grow our environment and they want me to look into a new platform that will give more saturation (somewhere in the upper 20's and low 40's). I've been looking at a Dell R900 (4 socket, 4 cores) /w 64 GB (ESX 3i with no local disks) of memory but with my current scenario issues, I'm not sure I'll get the saturation they're looking for with the R900 as I have it configured. Can anyone shed some light on this for me since I'm trying to fix the current environment and plan for the upcoming environment.
Thanks,
Roger
No you are doing it correctly - 6 vCPUs per core is a good mark to aim for since VMware recommends 4-8 - but that is going to depend on the load placed on by the VMs - the ones who are dirving 8-10 I would say they are lighly loaded potentially VDI - yes with only 16 GB I think is memory where you will find contention - check the perfomance graphs for balloon activity this will be an indication if you are running out of memry -
Hello,
Are you talking about VMware ESXi or VMware ESX? Note that ESXi does not support the full VMware Clustering suite only ESX does that. So you may want to make sure you are discussing the one you wish to use.
But sizing ESXi is the same as sizing ESX and as weinstein5 stated, it looks fine.
Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Edward,
The current platform is ESX 3.5 and the intended platform is ESX 3i for the new servers. I'm a little confused on what you say about the Clustering suite? From what I read I though ESX 3i offered the same feature set as standard ESX in a VMWare Cluster (DRS, HA, Vmotion). Are you saying this is not the case? Can you point me to some docs or a post so I don't waste your time explaining.
Thanks,
Roger
What he is referring to is that ESX 3i does not come with the licenses for vMotion, DRS or HA - you will need to buy those seperately -
You can't currenty mix ESXi with ESX 3.0 / 3.5 HA clusters - http://kb.vmware.com/kb/1004656.
Networking differences - http://kb.vmware.com/kb/103345. The networking KB article is for ESXi 3.5, but the ESXi 3.5 Update 1 release notes don't mention any changes.