Book Image

vSphere High Performance Cookbook - Second Edition - Second Edition

By : Kevin Elder, Christopher Kusek, Prasenjit Sarkar
Book Image

vSphere High Performance Cookbook - Second Edition - Second Edition

By: Kevin Elder, Christopher Kusek, Prasenjit Sarkar

Overview of this book

vSphere is a mission-critical piece of software for many businesses. It is a complex tool, and incorrect design and deployment can create performance related issues that can negatively affect the business. This book is focused on solving these problems as well as providing best practices and performance-enhancing techniques. This edition is fully updated to include all the new features in version 6.5 as well as the latest tools and techniques to keep vSphere performing at its best. This book starts with interesting recipes, such as the interaction of vSphere 6.5 components with physical layers such as CPU, memory, and networking. Then we focus on DRS, resource control design, and vSphere cluster design. Next, you’ll learn about storage performance design and how it works with VMware vSphere 6.5. Moving on, you will learn about the two types of vCenter installation and the benefits of each. Lastly, the book covers performance tools that help you get the most out of your vSphere installation. By the end of this book, you will be able to identify, diagnose, and troubleshoot operational faults and critical performance issues in vSphere 6.5.
Table of Contents (17 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Choosing the correct vSphere HA cluster size


When vSphere 5 was introduced, we saw a significant change in the HA model, and that does relax the constraints on the size of your vSphere HA cluster. But, you may ask, what about storage bottlenecks while accessing the same storage via a larger cluster? We have VAAI to handle that now, and that being in the picture, it does not constrain you from choosing a larger cluster.

Also, a crucial factor is that a larger cluster creates more scheduling opportunities for DRS, and a bigger cluster does not impose a heavy lift on the cost. Does that mean, we suggest only a bigger cluster and not many smaller clusters? Well, not really. It all boils down to what you are going to use on that cluster and what is your requirement. If you are implementing View Manager and are going to use Linked Clone, then you are limiting yourself with eight hosts, as with Linked Clone only eight hosts can access one single file. This restriction is not there in vSphere 5.1...