My old friends in VMware’s performance team updated the hugely popular performance troubleshooting guide for vSphere with a vSphere 4.1 version. The previous version of this document has been viewed nearly 30,000 times to date, making it the most popular document ever produced by performance engineering. The vSphere 4.1 version has already been seen over 9,000 times which suggests its early popularity with a large audience.
This paper documents the flow used by VMware’s outbound performance engineering team when they are engaged to investigate a performance problem. The process is shown in flow charts that will lead the reader to a bottleneck. The problems associated with resource bottlenecks are documented in a “cause” and “solution” section towards the end of this publication.
Before I left VMware one of my friends in the VMware support organization told me that the first version of this document was instrumental in educating VMware support on the diagnosis of performance issues. Hal’s document became mandatory reading for anyone that faced a performance problem. With the help of Chethan, his teammate and one of my VMworld co-presenters, this update is surely to add even more value to this document.
This week a colleague of mine asked me to help out with a customer’s network design in his VMware environment. I have long possessed the kind of