RDGW next most common bottleneck RDCB large deployments during logonrestart storms RDWEB t ypically not limiting factor RD Role Service Scale Limitations RDSH Workload Configuration ID: 667016
Download Presentation The PPT/PDF document "RDSH: most common bottleneck" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
RDSH: most common bottleneckRDGW: next most common bottleneckRDCB: large deployments during logon/restart stormsRDWEB: typically not limiting factor
RD
Role Service Scale LimitationsSlide2
RDSH Workload Configuration LoginVSI
4.0 Workload
Light
Medium
HD
HeavySlide3
RDSH Test Configuration
RDSH VM1
10vCPU
31GB Memory
RDSH VM2
10vCPU
31GB Memory
RDSH VM3
10vCPU
31GB Memory
RDSH VM4
10vCPU
31GB Memory
System Under Test
Dell PowerEdge R720
Dual Socket 10C Intel
®
Xeon
®
processor E5-2600v2
40 Logical cores, 128 GB Memory
Light
Medium
HeavySlide4
Example: Sizing Tenant with 30 Medium UsersOn-Premises RDSH Sizing
Workload
Profile
Users/vCPU
Memory/user
Light
8
270 MB
Medium
5
450 MB
Heavy
4
630 MB
Processors:
30/5 = 6 vCPU
Memory:
450*30 = ~14GB
30 Users requires VMs with 6vCPUs,14GB Memory
On-PremisesSlide5
Example: Sizing 30 Medium Users On-Premises & Azure:Example: On-Premises to Azure Migration
Workload
Profile
On-Premises*
Users/vCPU
Azure *
Users/vCPU
On-Premises
Memory/user
Azure Memory/user
LoginVSI
Medium
5
4
450 MB
450MB
6vCPU,14GB Memory
On-Premises
8vCPU,14GB Memory
Azure
1x A4 VM
or
4x A2 VMs
*Azure VM uses AMD Opteron CPU’s and On-Premises setup uses Intel Xeon E5-2600 v2 CPU’sSlide6
RDSH & RDGW Scale Guidance Summary
Role Service
Light
Medium
Heavy
RD Session Host
6
users / vCPU
270 MB RAM / user
4
users / vCPU
450 MB RAM / user
2
users / vCPU
630 MB RAM / user
RD Gateway
200 connections / vCPU
1 Mbps / connection
200 connections / vCPU
1 Mbps / connection
200 connections / vCPU
1 Mbps / connectionSlide7
Logon Storm Scenario (RDSH example)Adding RDSH servers to broker (e.g. broker restart)
Fixes available for WS2012 R2 also.
KB3091411
Connection Broker Scale Improvements
Connections
Initial burst
Connections
/sec
Success
Fail
Broker Mem
Before
Broker Mem After
Min connection
time (ms)
Max connection
time (ms)
Average connection time (ms)
WS2012
R2
10,000
100
2
2,319
7,681
43,696
1,480,144
5312,360,469
109,836
WS2016
10,0001002
10,000
02,532
22,284
78
4,062
214
Startup parameters
Server joins
Add times
(
ms)
# Servers
Delay (ms) between add
# Sess/server
Successful
Failed
Min
Max
Average
WS2012 R2
1,000
1,000
5
478
522
26,062
6,513,515
2,598,140
WS2016
1,000
1,000
5
1,000
0
281
16,141
2,108Slide8
SPLA and SALService Provider License Agreement (SPLA) allows partners to use RDS to host Windows desktops and applications using Windows Server.
RD
Subscriber Access License
(SAL) is paid to Microsoft monthly based on the number of users “authorized” to use the RDS-based service during the month.Slide9
RD License ServerActivate the serverSet to per-user modeEnter the SPLA number in add license wizard
Optional: Use RD license reports to help track usageSlide10
Stay CurrentSlide11
RD Team Blog – RD team lets you know of new features and capabilities, hotfixes, etc.Azure Blog – latest Azure capabilities announced
Keep Up with a Fast Changing WorldSlide12
© 2016 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.