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

Avoiding the use of a resource pool as a folder structure


It is common to use resource pools to create a folder structure in the host, have a cluster view of vCenter, and categorize your VMs. Administrators may place these VMs into these resource pools for sorting, but this is not the true sense of using resource pools. Resource pools should be used to prioritize VM workloads and guarantee and/or limit the number of resources available to a group of VMs. The issue is that even though a particular resource pool may have a higher level of shares, by the time the pool is subdivided, the VM ends up with fewer shares than a VM that resides in a resource pool with a lower number of shares.

If you create a resource pool with the default settings, then by default, this resource pool will be assigned 4,000 shares. Also, a VM has a default of 1,000 shares. In this way, if you place three VMs on a resource pool, even with default settings, the resources will be divided by three. This means that each...