Windows Server 2012 Hyper-V Deep Dive - Net

Windows Server 2012 Hyper-V Deep Dive Jeff Woolsey (#wsv_guy) Windows Server & Cloud

Régis Laurent Director of Operations,

Global Knowledge Competencies include: Gold Learning Silver System Management

Hyper-V in Windows Server 2012 Scale Performance and Density Mission Critical, Scale Up Workloads

Storage Investments in File & Block

More Secure Multi-Tenancy Flexible Infrastructure Continuous Availability VM Mobility

Windows Server 2008 R2 Editions… Maximum Processors

Maximum Memory

Failover Clustering and MultiPath IO Virtualized Server Guest OS Instances Licensed

Windows Server 2008 R2 Standard

Windows Server 2008 R2 Enterprise

Windows Server 2008 R2 Datacenter

Up to 4

Up to 8

Up to 64

Up to 32 GB

Up to 2 TB

Up to 2 TB

No

Yes

Yes

1

4

Unlimited

Per Server

Per Server

Per Processor

Windows Server 2012: Simplicity Windows Server 2012 Standard and Datacenter Editions share the same capabilities Scale Up to 64 physical processors, up to 4 TB physical memory Up to 64 virtual processors per VM, up to 1 TB memory per VM

Roles Active Directory, File Server, Hyper-V, IIS, Remote Access, all there…

Features BranchCache, BitLocker, Failover Clustering, MPIO, all there…

The only difference is virtualization licensing Standard: Two instances of Windows Server Datacenter: Unlimited instances of Windows Server

Windows Server 2012 Editions… Windows Server 2012 Standard

Windows Server 2012 Datacenter

Up to 64

Up to 64

Up to 4 TB

Up to 4 TB

Failover Clustering and Multi-Path IO

Yes

Yes

Windows Server Guest OS Instances

2

Unlimited

Per Processor

Per Processor

Maximum Processors

Maximum Memory

Licensed

Mission Critical Workloads

Scaling up: Physical NUMA NUMA (Non-uniform memory access)

NUMA node 1

NUMA node 2

Processors

Helps hosts scale up the number of cores and memory access Partitions cores and memory into “nodes” Allocation and latency depends on the memory location relative to a processor

Memory

High performance applications detect NUMA and minimize crossnode memory access Host NUMA

Scaling up: Physical NUMA

NUMA node 1

NUMA node 2 Processors

This is optimal… Memory allocation and thread allocations within the same NUMA node Memory populated in each NUMA node

Memory

NUMA node 3

NUMA node 4 Processors

Memory

Host NUMA

Scaling up: Physical NUMA

NUMA node 1

NUMA node 2 Processors

This isn’t optimal… System is imbalanced Memory allocation and thread allocations across different NUMA nodes Multiple node hops Node 2: odd number of DIMMS Node 3: insufficient memory Node 4: no local memory (worst case)

Memory

NUMA node 3

NUMA node 4 Processors

Memory

Host NUMA

Scaling Up: Guest NUMA Guest NUMA Presenting NUMA topology within VM Guest operating systems & apps can make intelligent NUMA decisions about thread and memory allocation

Guest NUMA nodes are aligned with host resources Policy driven per host – best effort, or force alignment

vNUMA node A vNUMA node B

vNUMA node A vNUMA node B

NUMA node 1 NUMA node 2 NUMA node 3 NUMA node 4

Hyper-V Scale Comparison Windows Server 2008

Windows Server 2008 R2

Windows Server 2012

16 LPs

64 LPs

320 LPs

Physical Memory Support

1 TB

1 TB

4 TB

Virtual Machine Processor Support

Up to 4 VPs

Up to 4 VPs

Up to 64 VPs

VM Memory

Up to 64 GB

Up to 64 GB

Up to 1 TB

Yes, one at a time

Yes, one at a time

Yes, with no limits. As many as hardware will allow.

No. Quick Storage Migration via SCVMM

No. Quick Storage Migration via SCVMM

Yes, with no limits. As many as hardware will allow.

16

16

64

16 Nodes up to 1000 VMs

16 Nodes up to 1000 VMs

64 Nodes up to 8000 VMs

HW Logical Processor Support

Live Migration Live Storage Migration Servers in a Cluster Cluster Scale

Linear Performance & Scale ESG Labs Validation: Windows Server 2012 with SQL Server 2012 The sum of the number of transactions processed per second and the average response time for the 10 transaction types were monitored as virtual CPUs were added from 4-64. The OLTP workload and concurrent user counts remained constant. The number of brokerage transactions per second scaled linearly up to 64 virtual processors.

Customer input on Storage

Hyper-V: Over 1 Millions IOPs from a Single VM Industry Leading IO Performance • VM storage performance on par with native • Performance scales linearly with increase in virtual processors • Windows Server 2012 Hyper-V can virtualize over 99% of the world’s SQL Server. Windows Server 2008 R2

Windows Server 2012

250,000 IOPs

1,000,000+ IOPs

Without Offloaded Data Transfer (ODX) Traditional data copy model Server issues read request to SAN Data is read into memory Data is written from memory to SAN

Problems Increased CPU & memory utilization Increased storage traffic Inefficient for SAN

VHD Stack

Offloaded Data Transfer (ODX) Offload-enabled data copy model Server issues offload read request to SAN SAN returns token representing request Server issues write request to san using token SAN completes data copy internally SAN confirms data was copied

Reduce maintenance time Merge, mirror, VHD/VHDX creation

Increased workload performance VMs are fully ODX-aware and enabled

VHD Stack

Hyper-V ODX Support Creation of a 10 GB Fixed Disk

Secure Offloaded data transfer Fixed VHD/VHDX Creation Dynamic VHD/VHDX Expansion

VHD/VHDX Merge Live Storage Migration

Just one example…

~3 Minutes

200 150 100 50 0

Time (seconds) Average Desktop

ODX