Terminal Servers on 64-bit Windows Stages.


52 views
Uploaded on:
Category: Fashion / Beauty
Description
Group Website: www.wtstek.com. Question. Would I be able to pimp my terminal servers by relocating ... Windows Server 2003 Family. n/a. Up to 4-way, 32 GB RAM. Up to 4-way, 4 ...
Transcripts
Slide 1

PubForum 2006, Brussels • Belgium

Slide 2

Terminal Servers on 64-bit Windows Platforms Bernhard Tritsch Microsoft MVP – Terminal Server Community Website: www.wtstek.com

Slide 3

Question Can I pimp my terminal servers by moving them to 64-bit Windows? PubForum 2006, Brussels • Belgium

Slide 4

TRITSCH: 64-BIT TERMINAL SERVERS Windows Server 2003 Family PubForum 2006, Brussels • Belgium

Slide 5

TRITSCH: 64-BIT TERMINAL SERVERS PubForum 2006, Brussels • Belgium

Slide 6

TRITSCH: 64-BIT TERMINAL SERVERS 32-bit Applications 32-bit Applications 64-bit Applications 32-bit Windows 64-bit Windows 64-bit Windows 32-bit Drivers 64-bit Drivers 64-bit Drivers 32-bit Drivers 32-bit Drivers Devices x64 and Itanium x86 and x64 PubForum 2006, Brussels • Belgium

Slide 7

TRITSCH: 64-BIT TERMINAL SERVERS User Mode 32-bit Application 64-bit Application WOW64 Windows Server 2003 x64 Edition Kernel Mode 64-bit Device Driver PubForum 2006, Brussels • Belgium

Slide 8

TRITSCH: 64-BIT TERMINAL SERVERS 32-bit Memory Tuning Boot.ini switches/3GB permits 3 GB for User und 1 GB for Kernel Mode/USERVA permits more granular memory mgmt. PAE (Physical Address Extension) Relies on particular equipment highlights, CPU has 36-bit address transport Mapping of virtual 32-bit to physical 36-bit addresses AWE (Address Windowing Extensions ) Set of APIs used to address virtual memory >4GB Applications require particular code PAE and AWE expend CPU execution!!! PubForum 2006, Brussels • Belgium

Slide 9

TRITSCH: 64-BIT TERMINAL SERVERS 32-bit Support on x64 Windows on Windows 64 (WoW64) 64-bit Windows underpins the execution of 32-bit applications by utilizing WoW64 Performance impediments? Considerable on Itanium Minimal or non on x64 No backing of… utilizations utilizing a 16-bit installer applications requiring a 32-bit framework channel driver or whatever other 32-bit piece mode drivers PubForum 2006, Brussels • Belgium

Slide 10

TRITSCH: 64-BIT TERMINAL SERVERS What\'s WOW64 doing? Confinement of 32-bit applications from 64-bit applications while keeping up information trade functionalities and interoperability Converting framework calls (Thunking) Mapping of I/O information streams from 32-bit applications to 64-bit drivers PubForum 2006, Brussels • Belgium

Slide 11

TRITSCH: 64-BIT TERMINAL SERVERS What\'s WOW64 doing? Mapping of utilizations memory into 64-bit framework address space Coordination of COM and RPC correspondence Application correspondence utilizing duplicate and glue Redirection of record and registry access – this is a truly intriguing point! PubForum 2006, Brussels • Belgium

Slide 12

TRITSCH: 64-BIT TERMINAL SERVERS Redirection of File Access Applications 32-bit applications  %SystemDrive%\Program Files (x86) 64-bit applications  %SystemDrive%\Program Files System documents 32-bit System records  %windir%\syswow64 64-bit System records  %windir%\system32 PubForum 2006, Brussels • Belgium

Slide 13

TRITSCH: 64-BIT TERMINAL SERVERS PubForum 2006, Brussels • Belgium

Slide 14

TRITSCH: 64-BIT TERMINAL SERVERS Registry Access x64 has one physical registry, however a consistent perspective of 32-bit and 64-bit zones individually Redirection: Registry access from 32-bit applications is diverted to a particular hub (WoW6432Node in HKLM\Software) Reflection: Mirroring of some 32-bit and 64-bit registry territories to synchronize framework settings (last compose wins) PubForum 2006, Brussels • Belgium

Slide 15

TRITSCH: 64-BIT TERMINAL SERVERS PubForum 2006, Brussels • Belgium

Slide 16

TRITSCH: 64-BIT TERMINAL SERVERS But shouldn\'t something be said about Memory? Expanded memory use!!! Information structures are greater on x64 stages System record reserve requires to twofold memory for practically identical execution on 32-bit frameworks PubForum 2006, Brussels • Belgium

Slide 17

TRITSCH: 64-BIT TERMINAL SERVERS PubForum 2006, Brussels • Belgium

Slide 18

TRITSCH: 64-BIT TERMINAL SERVERS Now it\'a about time to begin discussing versatility PubForum 2006, Brussels • Belgium

Slide 19

TRITSCH: 64-BIT TERMINAL SERVERS Scalability – Benchmarking Microsoft has a specific "history" in regards to TS benchmarks and coming about white papers New white papers incorporate prevalently relative results instead of outright numbers: "64-bit frameworks are x% superior to anything 32-bit frameworks" Not memory, yet CPUs or information I/O turned out to be the constraining variables… if there was sufficient memory accessible on the framework PubForum 2006, Brussels • Belgium

Slide 20

TRITSCH: 64-BIT TERMINAL SERVERS Microsoft Test – 8-Way Server, 40 GB RAM PubForum 2006, Brussels • Belgium

Slide 21

18% Presentation Server x64 Edition Presentation Server 4.0 60% 112% 116% TRITSCH: 64-BIT TERMINAL SERVERS Citrix Marketing Slide... PubForum 2006, Brussels • Belgium

Slide 22

TRITSCH: 64-BIT TERMINAL SERVERS But I needed to do my own tests... PubForum 2006, Brussels • Belgium

Slide 23

TRITSCH: 64-BIT TERMINAL SERVERS Test Environment Clients Test servers: double center CPUs, 4 – 16 GB RAM Microsoft Windows Server 2003, 32-bit und 64-bit Editions 10 double CPU test customers with 4 GB RAM going about as burden makers 1 PC utilized for checking and controlling the tests Control Test server 32-bit Test server 64-bit PubForum 2006, Brussels • Belgium

Slide 24

TRITSCH: 64-BIT TERMINAL SERVERS Apps and Test Sequence Applications (dispatched after client logon) After 10 seconds: Notepad.exe, ANSI test record, 8.4 KB After 30 seconds: Adobe Acrobat Reader 7, PDF archive, 3.8 MB After 50 seconds : Microsoft Word 2003, DOC report, 3.1 MB Create new session consistently PubForum 2006, Brussels • Belgium

Slide 25

TRITSCH: 64-BIT TERMINAL SERVERS PubForum 2006, Brussels • Belgium

Slide 26

TRITSCH: 64-BIT TERMINAL SERVERS PubForum 2006, Brussels • Belgium

Slide 27

TRITSCH: 64-BIT TERMINAL SERVERS PubForum 2006, Brussels • Belgium

Slide 28

TRITSCH: 64-BIT TERMINAL SERVERS PubForum 2006, Brussels • Belgium

Slide 29

TRITSCH: 64-BIT TERMINAL SERVERS PubForum 2006, Brussels • Belgium

Slide 30

TRITSCH: 64-BIT TERMINAL SERVERS PubForum 2006, Brussels • Belgium

Slide 31

32-bit, 2 Cores, 4 GB 200 dynamic sessions 1,400 procedures 43,000 setting switches every second 125 x Command shell 123 x Notepad 118 x Acrobat Reader 112 x WinWord 64-bit, 2 Cores, 4 GB 159 dynamic sessions 1,100 procedures 35,000 connection switches every second 102 x Command shell 99 x Notepad 98 x Acrobat Reader 86 x WinWord TRITSCH: 64-BIT TERMINAL SERVERS 32-bit and 64-bit (Intel) However, just 20-25 clients in a generation situation PubForum 2006, Brussels • Belgium

Slide 32

64-bit, 4 Cores, 16 GB 270 dynamic sessions 2,500 procedures 64,000 setting switches every second 228 x Command shell 223 x Notepad 222 x Acrobat Reader 214 x WinWord 64-bit, 4 Cores HT, 16 GB 341 dynamic sessions ca. 2,900 procedures 60,000 setting switches every second 252 x Command shell 241 x Notepad 238 x Acrobat Reader 231 x WinWord TRITSCH: 64-BIT TERMINAL SERVERS 64-bit Results (Intel) PubForum 2006, Brussels • Belgium

Slide 33

64-bit, 4 Cores, 8 GB 171 dynamic sessions 1,700 procedures 45,000 connection switches every second 165 x Command shell 164 x Notepad 158 x Acrobat Reader 149 x WinWord 64-bit, 4 Cores, 16 GB 322 dynamic sessions 2,900 procedures 70,000 connection switches every second 264 x Command shell 261 x Notepad 256 x Acrobat Reader 252 x WinWord TRITSCH: 64-BIT TERMINAL SERVERS 64-bit Results (AMD) PubForum 2006, Brussels • Belgium

Slide 34

32-bit, 4 Cores, 16 GB 319 dynamic sessions 2,800 procedures 70,000 setting switches every second 243 x Command shell 243 x Notepad 243 x Acrobat Reader 237 x WinWord NOTE: PAE switch, however just up to ~ 8 GB can be utilized When hitting the 8 GB restrict, the page peruses every second expanded signifficantly an ideal opportunity to open the client session and dispatch the applications effectively was any longer contrasted with 64-bit frameworks TRITSCH: 64-BIT TERMINAL SERVERS 32-Bit Results (AMD) PubForum 2006, Brussels • Belgium

Slide 35

64-Bit, AMD, 16 GB RAM 32-Bit, AMD, 16 GB RAM PubForum 2006, Brussels • Belgium

Slide 36

TRITSCH: 64-BIT TERMINAL SERVERS Reality Check Additional test in a genuine client environment Initial setup with 32-bit frameworks Dual Xeon 3.2 GHz with 4 GB Application profile: Microsoft Office, Lotus Notes, a few bank-particular applications, (for example, Java application J2SE) Result with 64-bit frameworks +25% clients on Dual Xeon 3.2 GHz with 8 GB +50% clients on 2 x Dual Core Xeon DP 2.8 GHz with 8 GB PubForum 2006, Brussels • Belgium

Slide 37

TRITSCH: 64-BIT TERMINAL SERVERS Performance 16 12 8 4 32-bit framework Memory (in GB) 64-bit framework PubForum 2006, Brussels • Belgium

Slide 38

TRITSCH: 64-BIT TERMINAL SERVERS Migration – how and when? Moving terminal servers from 32-bit to 64-bit is not as simple as it appears Challenges – 64-bit incompatibilities Installation schedules Drivers and framework instruments (Resource Kit apparatuses) Scripts adjusting framework documents and registry PubForum 2006, Brussels • Belgium

Slide 39

TRITSCH: 64-BIT TERMINAL SERVERS So, what\'s the outcome? Begin relocating now 64-bit is the future – that is without a doubt The innovation is developed... ...in any case, you will require some an opportunity to get settled with it PubForum 2006, Brussels • Belgium

Slide 40

TRITSCH: 64-BIT TERMINAL SERVERS Additional Information Terminal Server Capacity and Scaling http://www.microsoft.com/windowsserver2003/techinfo/outline/tsscaling.mspx Terminal Services Scaling and Performance on x64-Based Versions of Windows Server 2003 http://www.microsoft.com/windowsserver2003/advances/terminalservices/default.mspx Bernhard Tritsch\'s Terminal Server versatility assessment http://www.wtstek.com/item2/Article20041125.htm The Big Iron Test - Scalability of Large Terminal Server Platforms http://www.visionapp.de/fileadmin/records/English_ docu

Recommended
View more...