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

Improving network performance using network I/O control


The 1 GigE era is coming to an end and is rapidly being replaced by 10 GigE. This means less physical network connections and that network traffic with different patterns and needs will merge together on the same network.

This may directly impact performance and predictability due to lack of isolation, scheduling, and arbitration. Network I/O control can be used to prioritize different network traffic on the same pipe.

You cannot have guaranteed bandwidth as long as you don't limit other traffic, so there'll always be enough available bandwidth.

As some traffic (that is, vMotion) might not be used all the time, we'll have temporarily unused bandwidth with static limits. As long as there is no congestion, this doesn't really matter, but if there is, then you're limiting the bandwidth for traffic even when there is bandwidth available, which is not a good way to deal with congestion.

For some VMkernel traffic, VMware recommends dedicated...