Book Image

VMware Performance and Capacity Management, Second Edition - Second Edition

By : Sunny Dua
Book Image

VMware Performance and Capacity Management, Second Edition - Second Edition

By: Sunny Dua

Overview of this book

Performance management and capacity management are the two top-most issues faced by enterprise IT when doing virtualization. Until the first edition of the book, there was no in-depth coverage on the topic to tackle the issues systematically. The second edition expands the first edition, with added information and reorganizing the book into three logical parts. The first part provides the technical foundation of SDDC Management. It explains the difference between a software-defined data center and a classic physical data center, and how it impacts both architecture and operations. From this strategic view, it zooms into the most common challenges—performance management and capacity management. It introduces a new concept called Performance SLA and also a new way of doing capacity management. The next part provides the actual solution that you can implement in your environment. It puts the theories together and provides real-life examples created together with customers. It provides the reasons behind each dashboard, so that you get the understanding on why it is required and what problem it solves. The last part acts as a reference section. It provides a complete reference to vSphere and vRealize Operations counters, explaining their dependencies and providing practical guidance on the values you should expect in a healthy environment.
Table of Contents (28 chapters)
VMware Performance and Capacity Management Second Edition
Credits
Foreword
Foreword
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Part 1
Part 2
Part 3
Index

SDDC capacity planning


As the SDDC architect, you look at the big picture. Hence, it is important that you know your architecture well. One way to easily remember what you have is to keep it simple. Yes, you can have different host specifications—CPU speed, amount of RAM, and so on—in a cluster. But that would be hard to remember if you have a large farm with many clusters.

You also need to know what you actually have at the physical layer. If you don't know how many CPUs or how much RAM the ESXi host has, then it's impossible to figure out how much capacity is left. Sounds obvious, right? Who does not know how much physical resource he has!

Well, it's not so easy, actually.

We will use storage as an example to illustrate why it is hard to know what you actually have. Do you know how many IOPS your storage actually has?

Indeed. You only know roughly. There are too many "it depends" factors in the answer.

Once you know the actual raw capacity, you are in a position to figure out the usable portion...