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 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
Sunny Dua Sunny Dua
Author Profile Icon Sunny Dua
Sunny Dua
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 (20) Chapters Close

Preface Part 1 FREE CHAPTER
1. VM – It Is Not What You Think! 2. Software-Defined Data Centers 3. SDDC Management 4. Performance Monitoring 5. Capacity Monitoring Part 2
6. Performance-Monitoring Dashboards 7. Capacity-Monitoring Dashboards 8. Specific-Purpose Dashboards 9. Infrastructure Monitoring Using Blue Medora 10. Application Monitoring Using Blue Medora Part 3
11. SDDC Key Counters 12. CPU Counters 13. Memory Counters 14. Storage Counters 15. Network Counters Index

Some well-meaning but harmful advice

Can you figure out why the following statements are wrong? They are all well-meaning pieces of advice on the topic of capacity management. I'm sure you have heard them, or even given them.

Regarding cluster RAM:

  • We recommend a 1:2 overcommit ratio between physical RAM and virtual RAM. Going above this is risky.
  • Memory usage on most of your clusters is high, around 90 percent. You should aim for 60 percent as you need to consider HA.
  • Active memory should not exceed 50-60 percent. You need a buffer between active memory and consumed memory.
  • Memory should be running at a high state on each host.

Regarding cluster CPU:

  • The CPU ratio in cluster X is high at 1:5, because it is an important cluster.
  • The rest of your clusters' overcommit ratios look good as they are around 1:3. This gives your some buffer for spike and HA.
  • Keep the overcommitment ratio at 1:4 for tier 3 workload.
  • CPU usage is around 70 percent on cluster Y. Since they are User Acceptance Testing...
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