Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
VMware vRealize Operations Performance and Capacity Management

You're reading from   VMware vRealize Operations Performance and Capacity Management A hands-on guide to mastering performance and capacity management in a virtual data center

Arrow left icon
Product type Paperback
Published in Dec 2014
Publisher
ISBN-13 9781783551682
Length 276 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Iwan 'e1' Rahabok Iwan 'e1' Rahabok
Author Profile Icon Iwan 'e1' Rahabok
Iwan 'e1' Rahabok
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. Virtual Data Center – It's Not a Physical Data Center, Virtualized FREE CHAPTER 2. Capacity Management in SDDC 3. Mastering the Key Counters in SDDC 4. CPU Counters 5. Memory Counters 6. Network Counters 7. Storage Counters 8. Dashboard Examples and Ideas Index

Storage contention guidance


The following table provides general guidance on storage contention. It must be read in conjunction with the CPU Contention Guidance section in Chapter 4, CPU Counters. I must emphasize that these are just guidelines—you should set the values according to the unique needs of your environment.

Object

Contention

Remarks

VM

Official SLA:

  • Tier 1: 10 milliseconds

  • Tier 2: 20 milliseconds

  • Tier 3: 30 milliseconds

Internal threshold:

  • Tier 1: 5 milliseconds

  • Tier 2: 15 milliseconds

  • Tier 3: 20 milliseconds

The internal threshold is lower as it serves as a buffer.

Your customers only care about their own VMs, so the following numbers are for your internal targets. You should have a more stringent internal threshold. This gives you a buffer to troubleshoot.

Object

Contention

Remarks

ESXi

NA

There is no need to track at this level because of the following reasons:

  • You already track contention at the VM level, datastore level, and array level.

  • VMs get vMotion-ed in the cluster...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image