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 now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
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
Hyper-V 2016 Best Practices

You're reading from   Hyper-V 2016 Best Practices Harness the power of Hyper-V 2016 to build high-performance infrastructures that suit your needs

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher Packt
ISBN-13 9781785883392
Length 246 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Benedict Berger Benedict Berger
Author Profile Icon Benedict Berger
Benedict Berger
Romain Serre Romain Serre
Author Profile Icon Romain Serre
Romain Serre
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. Accelerating Hyper-V Deployment FREE CHAPTER 2. Deploying Highly Available Hyper-V Clusters 3. Backup and Disaster Recovery 4. Storage Best Practices 5. Network Best Practices 6. Highly Effective Hyper-V Design 7. Hyper-V Performance Tuning 8. Management with System Center and Azure 9. Migration to Hyper-V 2016

Performance tuning


After establishing performance counter baselines, it's time to interpret them. The values of networking, disks, and memory are self-explanatory, so let's go into the details of CPU sizing.

If the logical processor counter is low, but the virtual processor counter is high, it means that you can add more vCPUs to your virtual machines, as the logical processors are still available.

Theoretically, there is really no upper limit to how many virtual CPUs you can assign to virtual machines. The Microsoft recommendation is to not exceed more than 8 virtual CPUs per physical CPU core for server workloads and more than 12 virtual CPUs per physical CPU core for VDI workloads. However, there is no support limit, and there are low-workload scenarios where this recommendation can be extended.

My real-world experience from working with performance counters and baselines is to use a 1:4 ratio for production workload as a rule of thumb and a 1:12 ratio for Test/VDI workloads as a sizing...

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