Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
VMware Performance and Capacity Management, Second Edition

You're reading from   VMware Performance and Capacity Management, Second Edition Master SDDC Operations with proven best practices

Arrow left icon
Product type Paperback
Published in Mar 2016
Publisher
ISBN-13 9781785880315
Length 546 pages
Edition 2nd Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
 Dua Dua
Author Profile Icon Dua
Dua
 Rahabok Rahabok
Author Profile Icon Rahabok
Rahabok
Arrow right icon
View More author details
Toc

Table of Contents (28) Chapters Close

VMware Performance and Capacity Management Second Edition
Credits
Foreword
Foreword
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Part 1
Part 2
Part 3
1. VM – It Is Not What You Think! FREE CHAPTER 2. Software-Defined Data Centers 3. SDDC Management 4. Performance Monitoring 5. Capacity Monitoring 6. Performance-Monitoring Dashboards 7. Capacity-Monitoring Dashboards 8. Specific-Purpose Dashboards 9. Infrastructure Monitoring Using Blue Medora 10. Application Monitoring Using Blue Medora 11. SDDC Key Counters 12. CPU Counters 13. Memory Counters 14. Storage Counters 15. Network Counters Index

Contention versus utilization


Because each layer has its own set of requirements, this translates into two sets of counters or metrics. Each group has its own metrics.

At the VM layer, we care whether a particular VM is being served well by the platform. Other VMs are irrelevant from the VM owner's point of view. So the key counter here is VM contention. Infrastructure metrics are irrelevant here. Only when we are satisfied that there is no contention can we proceed to check whether the VM is sized correctly or not. Most people check for utilization first because that is what they are used to monitoring in the physical infrastructure. In a virtual environment, we should check for contention first.

At the Infrastructure layer, we care whether it serves everyone well. Make sure that there is no contention for resources among all the VMs in the platform. Only when the infrastructure is clear from contention can we troubleshoot a particular VM. If the infrastructure is having a hard time serving...

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 $15.99/month. Cancel anytime
Visually different images