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

Network

From the point of view of performance and capacity management, network has different fundamental characteristics than compute or storage. The key differences are summarized in the following table:

Compute or storage

Network

A relatively high amount of resources available to the VM

A low amount of resources available

Granular resource allocation at the VM level

Coarse allocation

Single-purpose hardware

Multi-purpose hardware

A node

An interconnect

Let's understand these differences in more detail, starting from the first one:

At the end of the day, the net resources available to the VMs is what we care about. What the ESXi and IaaS platform use is considered an overhead.

An ESXi host has a fixed specification (for example, two CPUs, 36 cores, 256 GB of RAM, two 10 GE NICs). This means that we know the upper physical limit. How much of that it available to the VMs? Let's take a look:

  • For compute, the hypervisor consumes a relatively low proportion of resources. Even...
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