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 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
 Rahabok Rahabok
Author Profile Icon Rahabok
Rahabok
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

VMware vRealize Operations Performance and Capacity Management
Credits
Foreword
Foreword
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
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

Memory contention guidance


The following table provides a general guidance on memory contention. It must be read in conjunction with the CPU contention guidance section from the previous chapter. I must emphasize that this is just a guideline, which needs to be adjusted to meet the needs of your environment.

Object

Contention

Remarks

VM

  • Tier 1: 0 percent

  • Tier 2: 5 percent

  • Tier 3: 10 percent

Because every single VM has its memory backed by the hypervisor, there will be no ballooning, swap, or compression. As a result, the value for Contention in tier 1 will be 0 percent.

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

Object

Contention

Remarks

ESXi

NA

Please see the CPU contention guidance section from the previous chapter as the same logic applies here.

Cluster

Internal threshold:

  • Tier 1: 0 percent...

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