Posted by Simon Long Mar 12, 2012
VMware Configuration Maximums – Not Targets
Something I've noticed a lot work creating designs for customers is the customer focusing on vSphere Configuration Maximums and the aim to reach those maximums. This concerns me a lot when I hear this and also the regularity that I hear this.
VMware Configuration Maximum's are values that have been tested by VMware QA to verify that the product will function correctly.
Yes, this can mean that VMware's software may continue to function adequately above the maximums. However because this has not been tested, VMware cannot be certain it will function correctly and therefor will probably not support your business should you encounter issues.
Another thing to bare in mind is that these Configuration Maximum's are just that, they are the maximum you should go, they are the "Do not cross" or "trespassers maybe prosecuted". Configuration Maximums are not something for your business to aim for. Reaching a maximum does not mean you will get the best performance from your environment, although I'm sure some CFO's would disagree with me.
Conclusion
When designing your VMware vSphere/View/vCloud environment aim to stay well within the maximums, this will allow for unexpected growth without the need to make dramatic changes to your design. As a rule of thumb, where possible, allow for a 10% buffer between your environment maximums and the VMware Configuration Maximums, this will allow for administrative errors.
If you found this post useful make sure you subscribe to my RSS Feed: 
