1 / 36

virtual techdays

INDIA │ 18-20 august 2010. virtual techdays. Get the most out of your Hyper-V Deployment. Pracheta Budhwar │ Partner Technical Consultant, Microsoft. INDIA │ 18-20 august 2010. virtual techdays. Perceptions from the field External Publicly Available Information

zeki
Download Presentation

virtual techdays

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. INDIA │ 18-20 august2010 virtual techdays Get the most out of your Hyper-V Deployment Pracheta Budhwar │ Partner Technical Consultant, Microsoft

  2. INDIA │ 18-20 august2010 virtual techdays • Perceptions from the field • External Publicly Available Information • Hyper-V Performance Tips • Key Takeaways • Learn how to identify resource contention • Hyper-V is ready for the enterprise and is even better with WS08 Hyper-V R2 S E S S I O N A G E N D A

  3. INDIA │ 18-20 august2010 virtual techdays • Hyper-V can’t run that many VMs per box (I don’t get the density) • Hyper-V can’t perform under load • I can’t/won’t run my business critical applications like SQL, SharePoint and Exchange on Hyper-V Observations Heard from the Field Our customers and Partners • Try Hyper-V R2, it makes a big difference. • Don’t compare against R1 of Hyper-V • Windows Server 2008 R2 has incredible • performance • Hyper-V R2 is a phenomenal platform for • yourMicrosoft business critical apps • and your apps from other ISVs as well

  4. INDIA │ 18-20 august2010 virtual techdays Unisys Evaluation of Live Migration Performance

  5. INDIA │ 18-20 august2010 virtual techdays SQL Server Performance: SLAT impact • Configuration: • OS: Microsoft® Windows Server® 2008 R2 Hyper-V™ • Hardware: HP DL585 (16 core) with SLAT (Second Level Address Translation) processor architecture, HP EVA 8000 storage • Virtual Machines: 4 virtual processors and 7 GB RAM per virtual machine; Fixed size VHD • Results: • Increased throughput with consolidation • Near linear scale in throughput with no CPU over-commit • Improved performance with Windows Server 2008 R2 and SLAT processor architecture Heavy Load Moderate Load Low Load

  6. INDIA │ 18-20 august2010 virtual techdays Hyper-V Performance Tips 20 tips towards a better experience

  7. Root Partition Child Partition Child Partition Server Server VSPs VSPs I/OStack I/OStack I/OStack OS Kernel Enlightenments (WS08+) Drivers VSCs VSCs VMBus VMBus VMBus Shared Memory Hypervisor Devices Processors Memory INDIA │ 18-20 august2010 virtual techdays Hyper-V Architecture Review

  8. INDIA │ 18-20 august2010 virtual techdays #1 The 4 Primitives Know the 4 primitive resources of your server CPU MEM DISK NET

  9. INDIA │ 18-20 august2010 virtual techdays The 4 Primitives* Initial Indicators of Performance • CPU: • \Processor(*)\% Processor Time > 75% • Memory: • \Memory\Available MBytes < 100MBs • Disk • \LogicalDisk(*)\Avg Disk sec/Read|Write > 15ms • Network • \Network Interface(*)\Output Queue Length > 2 CPU MEM DISK NET

  10. INDIA │ 18-20 august2010 virtual techdays #2 • \Hyper-V Hypervisor Logical Processor(*)\% Total Run Time • \Hyper-V Hypervisor VirtualProcessor(*) • \% Guest Run Time • Healthy:less than 75% • Warning: greater than 75% • Critical:greater than 85% • Avoid Task Manager! • Avoid % Processor Time! Use Hyper-V Perf Counters For Physical Processors For Virtual Processors

  11. INDIA │ 18-20 august2010 Hyper-V Processor Utilization virtual techdays Root Partition (physical host) % Processor Time performance counters on the root partition are not accurate. Use the % Guest Run Time and % Total Run Time counters Root Partition % Processor Time 2 2% 5% 4% 3% Virtual BizTalk 1 % Processor Time 100% 100% 3 \ Hyper-V Hypervisor Logical Processor(*)\% Guest Run Time 90% 90% 90% 90% Virtual BizTalk 1 % Processor Time 100% 100% 4 \Hyper-V Hypervisor Logical Processor(*)\% Total Run Time 95% 95% 95% 95% % Processor Time performance counters on the root partition are not accurate. Use the % Guest Run Time and % Total Run Time counters

  12. INDIA │ 18-20 august2010 virtual techdays #3 2 to 1 Ratio 1 to 1 Ratio 1 2 BizTalk Server BizTalk Server BizTalk Server BizTalk Server Assess the Processor Ratios Virtual Processors Virtual Processors Virtual Processors Virtual Processors 0 0 0 0 1 1 BizTalk Server BizTalk Server BizTalk Server BizTalk Server Virtual Processors Virtual Processors Virtual Processors Virtual Processors 0 0 0 0 1 1 Logical Processors Logical Processors 0 0 1 2 3 1 2 3 Under utilized? Over utilized?

  13. INDIA │ 18-20 august2010 virtual techdays #4 • Install the Integration Components (ICs) • Dramatically improves overall workload performance • Check for the Virtual Machine Bus in Device Manager • ICs not needed running WS08 R2 as a guest Install Integration Components Runs even better on R2!

  14. INDIA │ 18-20 august2010 virtual techdays #5 Use Windows 2008 VMs • Use Windows Server 2008 and greater as the guest OS – fully enlightened • Enlightenments reduce the cost of OS functions like memory management • Direct HyperCalls to the Hypervisor Virtual Guest (Child Partition) Virtual Guest (Child Partition) Not optimal Optimal

  15. INDIA │ 18-20 august2010 virtual techdays #6 Use SLAT Processors • Use hardware that supports Second Level Address Translation (SLAT) • SLAT is hardware optimized for virtual environments • AMD calls this feature Rapid Virtualization Indexing • On Phenom and Opteron processors • Sometimes called Nested Page Tables (NPT) • Intel calls this feature Extended Page Tables (EPT) • Nehalem based processors which are Intel Core i7 for desktops and the Xeon 5500 series for servers.

  16. INDIA │ 18-20 august2010 virtual techdays Customer Processor Analysis with SLAT Compared physical SQL Server to virtual SQL Server Physical processor usage is 1% difference! Running 16-way Intel Nehalem x5550 WS08 R2 running on WS08 R2

  17. INDIA │ 18-20 august2010 virtual techdays #7 Close the Window on Managers • Hyper-V Manager and VMConnect sessions consume resources. • Close or minimize the Hyper-V Manager during testing. • Close VMConnect windows during testing. Hyper-V Manager VMConnect Session

  18. INDIA │ 18-20 august2010 virtual techdays #8 Use basic video drivers • Avoid high end video card drivers… for now. • High-end drivers (WDDM) cause heavy virtual to physical address translations. Optimal

  19. INDIA │ 18-20 august2010 virtual techdays #9 Avoidusing the Root Partition Avoid running services on the root partition (host machine)

  20. INDIA │ 18-20 august2010 virtual techdays #10 • \LogicalDisk(*)\Avg. Disk Sec/Read|Write • Healthy: less than 10ms (0.010) • Warning: greater than 15ms (0.015) • Critical: greater than 25ms (0.015) • \LogicalDisk(*)\Disk Transfers/sec • The IOPS from a Windows perspective For Reference: • Single 5400rpm spindle: ~14ms raw seek time with about 200 IOPS • 3.5” floppy: ~900ms* with about 1 IOPS Disk Response Time Still Rule!

  21. INDIA │ 18-20 august2010 virtual techdays #11 • Hyper-V runs great on Solid State Disks (SSD) in the field • Customer example: • SSD is able to do more I/O’s per second (IOPS) with faster response times • No slow downs with Hyper-V R2! • Less than 1ms spent in the Hyper-V Solid State is Faster! E: = SSD F: = non-SSD Higher Is Better SSD has more throughput! SSD has faster response times Lower Is Better

  22. INDIA │ 18-20 august2010 virtual techdays #12 AvoidSnapshots • Avoid using the Hyper-V snapshot feature unless on WS08 R2. • Great for quick backups, but… • Snapshots require additional overhead to track changes

  23. INDIA │ 18-20 august2010 virtual techdays #13 Use Pass-Thru Disk with SCSI Step 1: Take disk offline. • I/O passes straight to the storage stack on the root. • Best for high I/O services like SQL and Exchange. Step 2: Assign to child partition (VM) as SCSI.

  24. INDIA │ 18-20 august2010 virtual techdays #14 Use Fixed Size VHDs • If Pass-Thru disk is not possible, then use fixed size VHDs. • Better for performance, but consumes more physical disk storage than dynamic expanding.

  25. INDIA │ 18-20 august2010 virtual techdays #15 Disable Removable Media • Disable the removable media drives (floppy, optical drive, etc.) when not in use. • Removable media is polled periodically.

  26. INDIA │ 18-20 august2010 virtual techdays #16 Leave Memory for the Root • Leave at *least* 512MBs of RAM to the root partition. 1GB or more recommended. • Same with Server Core Edition

  27. INDIA │ 18-20 august2010 virtual techdays #17 Allocate Enough RAM • \Memory\Available MBytes: Measures available RAM • Healthy: greater than 10% of RAM • Warning: less than 10% of RAM • Critical: less than 100MBs • Applies to all physical and virtual computers. • High pages/sec alone does *not* indicate a low memory condition • See“The Case of the Phantom Hard Page Faults”

  28. INDIA │ 18-20 august2010 virtual techdays Root Partition (physical host) – 16GBs of RAM Root Partition (physical host) Virtual Guest VirtualGuest Memory Capacity Planning RAM: 4GBs RAM: 2GBs More RAM allows actively used memory to stay in RAM longer – less paging to disk Committed Memory Committed Memory Pagefile.sys Pagefile.sys Committed Memory

  29. INDIA │ 18-20 august2010 virtual techdays Memory Capacity Planning Virtual Guest Use “\Memory\Committed Bytes” as the starting point for RAM capacity planning RAM: 4GBs Committed Memory Physical Computer Pagefile.sys RAM: 2GBs Committed Memory – 2GBs Pagefile.sys

  30. INDIA │ 18-20 august2010 virtual techdays #18 AvoidNetwork Congestion • \Network Interface(*)\Output Queue Length • Healthy: less than 1 on average • Warning: greater than 1 on average • Critical: greater than 2 on average • Diagnose with Resource Monitor, xPerf, etc. • Add more physical NICs if congestion regularly occurs • Dedicated 1Gb physical NICs recommended for Live Migration. • Ref: Hyper-V: Live Migration Network Configuration Guide

  31. INDIA │ 18-20 august2010 virtual techdays #19 Avoidusing Legacy Adapters • Use synthetic network adapters (default). • Avoid legacy network adapters – gold colored plug icon. • Legacy adapters are better for compatibility (PXE boot, no ICs, etc.), but not as performing as synthetic. Legacy NIC Not optimal Synthetic NIC - default Optimal

  32. INDIA │ 18-20 august2010 virtual techdays #20 Use NIC Features in R2 • Virtual Machine Queues (VMQ) reduces overheads by reducing the cost of routing incoming packets, more optimized copy paths, and better interrupt distribution. • Chimney offload is helpful for long running connections. It also improves overhead by reducing copy path costs. • Requires Windows Server 2008 R2 • See the following article for more information: • Networking Deployment Guide: Deploying High-Speed Networking Features

  33. INDIA │ 18-20 august2010 virtual techdays Announcing PAL v2.0 Beta 1 • An easy to use tool that analyzes performance counter logs (*.blg) files and creates an HTML report for easy diagnoses • Easy counter analysis • Aware of Hyper-V counters • PAL v2.0 is now in Beta 1! • Open source and free

  34. INDIA │ 18-20 august2010 virtual techdays DEMO: DEMO TITLE PrachetaBudhwar│ Partner Technical Consultant, Microsoft

  35. INDIA │ 18-20 august2010 virtual techdays • Microsoft Performance Monitor • Microsoft xPerf • Performance Analysis of Logs (PAL) Tool • IOMeter TOOLS

  36. THANKS│18-20 august2010 virtual techdays Pracheta.budhwar@microsoft.com

More Related