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 the SDRS I/O metric and array-based automatic tiering together


While we can employ array-based automatic LUN tiering and VMware Storage DRS, we need to disable the I/O-metric-based calculation in SDRS. This way, we would not employ both of them for the same job. Now let's see what it does in the backend.

SDRS triggers action in either capacity and/or latency. Capacity stats are constantly gathered by vCenter, where the default threshold is 80 percent. I/O load trend is evaluated (by default) every 8 hours, based on the past day's history; the default threshold is 15 ms. This means that the Storage DRS algorithm will be invoked when these thresholds are exceeded. Now, in the case of utilized space, this happens when vCenter collects datastore statistics and notices that the threshold has been exceeded in the case of I/O load balancing.

Every 8 hours, Storage DRS evaluates the I/O imbalance and makes recommendations if and when the thresholds are exceeded. Note that these...