Guido Grillenmeier Senior Solution Architect Hewlett-Packard

Präsentation zum Thema: "Guido Grillenmeier Senior Solution Architect Hewlett-Packard"—  Präsentation transkript:

1 Guido Grillenmeier Senior Solution Architect Hewlett-Packard
3/28/2017 8:11 PM Windows Server 2008: 64-Bit-Versionen { Vorteile und Einsatzszenarien } Guido Grillenmeier Senior Solution Architect Hewlett-Packard © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

2 Agenda Intro zu 64-Bit Computing
3/28/2017 8:11 PM Agenda Intro zu 64-Bit Computing Intro zu x64 und Itanium Prozessor Architektur Unterschiede der 64-Bit Versionen in Windows Server 2008 32-Bit Apps in 64-Bit Windows Einsatzszenarien Zusammenfassung ©2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

3 Warum ist 64-Bit ein Thema HEUTE?
[Course Title] [Module Title] Warum ist 64-Bit ein Thema HEUTE? 32-Bit Technologie ist schon alt und wir stoßen immer öfters an deren Grenzen 1989: 486 DX, erster 32-bit Intel-Chip 1993: Windows NT 3.1, erstes 32-bit OS von Microsoft 64-Bit Technologie gibt es auch schon seit längerem – ein paar Beispiele: 1992: DEC ALPHA Prozessor - Windows NT (sogar für Windows 2000 in the Beta Phase) 1992: IBM PowerPC Prozessor 1995: SUN UltraSPARC Prozessor 1996: HP PA-RISC Prozessor auf 64-bit erweitert Microsoft hat alle Karten auf die 64-Bit Technologien gesetzt Ausgereifte 64-Bit Hardware schon längst verfügbar um die meisten Szenarien auf Windows zu unterstützen! DEC ALPHA b/w = 32-bit SW colored = 64-bit SW [Rev. # or date] – HP Restricted

4 Intro zu 64-Bit Computing
[Course Title] [Module Title] Intro zu 64-Bit Computing Execution Unit CPU Registers L1 Instr. Cache L2 Mem. Cache L3 Mem. Cache RAM Memory Wenn wir von 32-Bit oder 64-bit Prozessoren sprechen, meinen wir eigentlich die Anzahl der Bits, welche die Register im Prozessor speichern können Alle Daten die vom Prozessor verarbeitet werden sollen, müssen zuvor in einem Register gespeichert werden 64-Bit Prozessor = Register ist 64 Bit breit CPUs haben unterschiedliche Register, z.B. GPR und FÜR GPRs (General Purpose Registers) werden für zweierlei Datentypen verwendet: Integer Daten  die zu verarbeitenden Daten Adress Daten  Memory Pointers Die Register Breite der Memory Pointers ist einer der wesentlichen Vorteile von 64-Bit Prozessoren 32-bit Register adressieren direkt 232 Bits = 4 Giga-Bytes 64-bit Register adressieren direkt 264 Bits = 16 Exa-Bytes* = 16 Milliarden GB * 16 Exa-Bytes können zwar technisch mit 64-Bit adressiert werden, aber derzeit gibt es noch keine HW hierfür [Rev. # or date] – HP Restricted

5 Die Adressraum-Limitierungen in 32-Bit Windows
[Course Title] [Module Title] Die Adressraum-Limitierungen in 32-Bit Windows Mit 32-Bit Windows Server, werde die User Prozesse auf 4 GB virtuellen Adressraum limitiert 64-bit Systems hat ausreichend Adressraum für Kernel und User Prozesse 32bit apps on 64bit OS 12 GB 2 GB Kernel Memory User Memory 32-bit App1 4 GB User Memory 32-bit App3 /largeaddressaware User Memory 32-bit App2 Der Windows Kernel beansprucht die ersten 2 GB des Adressbereichs Kann mit /3GB and /UserVA Optionen in Boot.ini beinflusst werden Beschränkt den Adressbereich des Kernels Nur sinnvoll für APPs die mit der /LARGEADDRESSAWARE Compiler Option kompiliert wurden /3 GB switch 1 GB 3 GB Kernel Memory User Memory all 32-bit Apps Kernel Memory User Memory 2 GB 4 GB 32-bit Programme auf 64-bit Windows können jeweils bis zu 4GB User Adressraum in Anspruch nehmen Dies hat KEINEN negativen Einfluss auf den Kernel Adressraum 2 GB Virtual Address Space [Rev. # or date] – HP Restricted

6 Mehr zu den 32-Bit Limitierungen…
[Course Title] [Module Title] Mehr zu den 32-Bit Limitierungen… Auch heute schon können 32-Bit Windows Server mehr als 4 GB physikalischen Speicher nutzen Physical Addressing Extensions (PAE) und Address Windowing Extensions (AWE) muss von einer Applikation verwendet werden um mehr Speicher zu adressieren Nachteil: die Umwandlung zwischen virtuellem und physikalischem Speicher beeinflusst die Leistung 64-Bit Systeme eliminieren die 4 GB Speicher Grenze Der physikalische Speicher kann komplett direkt adressiert werden Server App Address Space Physical Memory 4 GB 12 GB AWE Window AWE Memory Server App Address Space Physical Memory 12 GB Server App Address Space 4 GB [Rev. # or date] – HP Restricted

7  Agenda Intro zu 64-Bit Computing
3/28/2017 8:11 PM Agenda  Intro zu 64-Bit Computing Intro zu x64 und Itanium Prozessor Architektur Unterschiede der 64-Bit Versionen in Windows Server 2008 32-Bit Apps in 64-Bit Windows Einsatzszenarien Zusammenfassung ©2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

8 [Course Title] [Module Title] x64 Architektur Intro basiert auf Intel x86 Architektur; wird in den meisten 32bit Intel Prozessoren heutiger Microsoft Windows Systeme verwendet x64 = Extended 64-bit Memory Technology entwickelt and zuerst von AMD (AMD64) in 2003 vorgestellt, gefolgt von Intel (EM64T) in 2004 Prozessor Architektur offiziell als AMD64 bezeichnet Haupt Merkmale Erweiterung GPR Breite von 32 Bit auf 64 Bit Ergänzung des bekannten x86 Instruction Set mit 64-Bit Funktionen Kann 32-bit x86 Code weiterhin native (direkt) ausführen 64-bit Erweiterungen sind bei Start nicht aktiv Kompatibel mit 32-bit und 64-bit OS und Verdoppelung the Register von 8 GPR und 8 SSE zu jeweils 16 16 GPR (64-bit) 8 GPR 32 bit x86 x64 8 SSE (80-bit) 16 SSE (80-bit) [Rev. # or date] – HP Restricted

9 [Course Title] [Module Title] Switching Modes in x64 Wichtiges Merkmal: die x64 Architektur kann in unterschiedlichen Modi operieren Neuer Modus Long Mode (unterscheided 64-Bit und 32-bit Basis Funktion) Ohne Long Mode, arbeitet der Prozessor im Legacy Mode als Standard 32-bit x86 Prozessor (kompatibel mit 32-bit OS und Apps) Long Mode unterscheidet zwei Sub-modes: 64-bit Mode (Native) und Compatibility Mode (für 32-bit Apps in einem 64-bit OS) Übersicht der x64 Prozessor Modes and Funktionen: Source: ADM x86-64TM Technology White Paper 9 [Rev. # or date] – HP Restricted

10 Itanium Architecture Intro
[Course Title] [Module Title] Itanium Architecture Intro Native 64-Bit Architektur, co-designed von Intel und HP 2001 vorgestellt; sollte HP's eigene PA-RISC Familie ersetzen und sowohl HP-UX als auch Windows OS betreiben Neue High Performance Wide-Word Architektur mit komplett neuem Instruction Set  EPIC: Explicitly Parallel Instruction Computing Grösserer Cache und Prediction Methoden reduzierten Speicher Zugriffszeiten Spezielle Reliability, Availability, und Serviceability (RAS) Funktionen Aktueller Release = Itanium2 (Montecito) Haupt Merkmale Deutlich mehr Register als x64 128 GPR (General Purpose) und FPR (Floating Point), 8 Branch Register Großer Level 3 Cache (bis 24MB) EPIC Instruction Set Immer 64-bit Muss 32-bit x86 Anweisungen zum Ausführen übersetzen Benötigt reines 64-bit Itanium OS (Windows, HP-UX, Linux, HP VMS) 128 GPR (64-bit) Itanium2 128 FPR (82-bit) 8 Branch (64-bit) [Rev. # or date] – HP Restricted

11 The Integrity Hardware-Error Story
Presentation Title The Integrity Hardware-Error Story Itanium hat leistungsstarke and speziell entwickelte Error-Handling Funktionen (RAS) welche der x86/x64 Hardware (z.B. HP Proliant Servers) überlegen ist HP Integrity Servers nutzen diese Vorteile für die zuverlässigsten Systeme mit Itanium Prozessoren… Insb. die Server mit Machine Check Architecture (MCA) Das Itanium Error-Handling Motto: “The strength of a Godzilla. The integrity of a Gandhi.” Windows Server können diese Features auch nutzen! rx7640 rx8640 Superdome NonStop 11

12 High Availability The three Itanium/Integrity strong points
Presentation Title High Availability The three Itanium/Integrity strong points 1. Diagnosability of all hardware crashes Upon H/W errors, trusted firmware code immediately logs a “Machine Check Abort” log with information on what failed and how it failed. 2. Error containment for errant hardware/software HP’s Integrity chipsets are explicitly designed to isolate and contain errant components immediately upon detection of an error 3. Monitor-ability for tracking corrected errors Corrected errors can occur periodically in healthy systems, but need to be tracked and trended by online diagnostics for predictive analysis CMC (Corrected Machine Checks) CPE (Corrected Platform Errors) 12

13 [Course Title] [Module Title] WOW64 Subsystem Windows x64 Erlaubt 64-Bit Windows Versionen die Ausfuehrung von 32-Bit Apps WOW64 32bit app Registry- und File-Redirection x64 Prozessor führt 32-Bit Code native aus WOW64 gibt Anweisungen direkt an HW Kein Performance Verlust Itanium Prozessor versteht die x86 Anweisungen nicht direkt: Muss erst in EPIC Anweisung umgewandelt werden; via Software Translator (IA-32 EL) Nicht für high performance 32-bit Apps ausgelegt x64 CPU Windows Itanium WOW64 32bit app IA-32 EL Itanium2 CPU WOW64 = Windows-Of-Windows64 IA-32 EL = Intel Architecture 32-bit Execution Layer [Rev. # or date] – HP Restricted

14 [Course Title] [Module Title] WOW64 Subsystem Diverse Verbesserungen im IA-32 EL in Windows Server 2008 (und Windows 2003 SP2) Emulation wird über mehrere Prozessoren parallel ausgeführt, statt das alle 32-bit Applikationen nur einen Prozessor verwenden Allgemein verbesserte Leistung durch Tuning und Code- Optimierung im IA-32 EL Bei Floating Point mit SSE-3 für 32-bit Apps deutlich leistungsfähiger (SSE-3 = Streaming SIMD Extensions) Verbesserte Zuverlässigkeit der Apps durch: Job Memory Limits (hindert „leaking Apps“ davon andere Apps zu beeinflussen) and Misalignment Notification Note: IA-32 EL ist dennoch fokussiert auf „leichte“ Apps (z.B. Administrations Tools und System Monitoring) Windows Itanium WOW64 32bit app IA-32 EL Itanium2 CPU [Rev. # or date] – HP Restricted

15 Haupt-Unterschiede x64 vs. Itanium
[Course Title] [Module Title] Haupt-Unterschiede x64 vs. Itanium Feature x64 Itanium2 Instruction Set Extended x86 EPIC OS Support Windows, Linux Windows, HP-UX, Linux, HP VMS Compatibility for Windows 32-bit apps Directly executes 32-bit x86 instructions Requires software based translation of 32-bit x86 instructions to EPIC RAS (reliability, availability, and serviceability) None YES Registers 16 GPR, 16 SSE 128 GPR, 128 FPR, 8 Branch Caches L1, L2 (up to 6MB) L1, L2, L3 (up to 24MB) Functional Units 10 Units (5 ALU, 1 STORE, 1 LOAD, 1 FPU, 1 BR, 1 3DNOW! [only AMD] ) 30 Units (6 ALU, 4 DCU, 1 ISHIFT, 6 PALU, 2 PSMU, 1 PMUL, 1 POPCNT, 2 FMA, 2 FSIR, 2 FMISC, 3 BR) Transistors on Chip Analogy: size of area required if using conventional wired transistors ~ 100,000,000 Analogy: ½ km2 ~1,700,000,000 Analogy: 15 km2 [Rev. # or date] – HP Restricted

16 Microsoft Windows Memory Architecture
Memory allocation settings 32-bit x86 64-bit x64/Itanium Total amount of virtual address space 4 GB 16 TB Amount of virtual address space per 32-bit process 2GB (3GB with /Largeadressaware) 2GB (4GB with /Largeadressaware) Amount of virtual address space for the 64-bit processes NA 8 TB Amount of paged pool memory 540 MB 128 GB Amount of non-paged pool memory 256 MB (128 MB w /3GB) Size of system cache 1 GB 1 TB

17 Vergleich des Speicher Adressraums
Heutige Speicher- und CPU-Limits Prozess-Adressraum 32-bit (2 GB/3GB) 64-bit (8 TB) – both x64 and Itanium HP DL 585 x64: 128 GB, 4 CPU-Slots HP Integrity Superdome Itanium: 2 TB, 64 CPU-Slots (targeting 4TB in WS2008 era)

18   Agenda Intro zu 64-Bit Computing
3/28/2017 8:11 PM Agenda  Intro zu 64-Bit Computing Intro zu x64 und Itanium Prozessor Architektur Unterschiede der 64-Bit Versionen in Windows Server 2008 32-Bit Apps in 64-Bit Windows Einsatzszenarien Zusammenfassung  ©2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

19 Windows Server 2008 Versionen
Server SKUs CPU Architect. max. Memory max. CPU slots* Server Core Built-In Virtuali-zation Virtual guests per lic. x86 x64 4 GB 32 GB 4 √ √** (x64) 1 64 GB 2 TB 8 √ (x64) 32 64 unlimited IA64 64 RTM Version von WS2008 wird Microsofts letztes 32-Bit Server OS sein WS2008 R2 nur als 64-Bit Version geplant Sogar die neuen SMB OS Versionen werden nur als 64-Bit released * Max Anzahl aller Cores = 64 / ** Standard Edition wird nicht alle Hyper-V Funktionen unterstützen

20 Windows Server mit 64 Cores… 

21 Windows Server 2008 für Itanium
Auf Enterprise Workloads abgestimmt: Datenbanken (MS SQL Server, Oracle, DB2,…) Line-of-Business Applikationen (SAP, SAS, Siebel,…) Eigenentwicklungen Rollen die nicht für diese Workloads geeignet sind, wurden aus dieser Windows Server 2008 OS Version entfernt Abgestimmt mit dem Bedarf der Enterprise Workloads Vorteile Nicht benötigter Code und Dienste wurden entfernt Reduzierter Patching-Aufwand Hochverfügbarkeit weiter gesteigert

22 64-bit Funktionen in Windows Server 2008
[Course Title] [Module Title] 64-bit Funktionen in Windows Server 2008 Role x64 Itanium Itanium Comment Active Directory Domain Services Yes No Can be a member in an AD domain Active Directory Lightweight Directory Services Can access AD LDS directories Active Directory Federated Services (ADFS) server Can be an ADFS client Application Server Fully supported Distributed File System Replication (DFSR) Can NOT host or access a DFSR share Dynamic Host Configuration Protocol (DHCP) Does have a DCHP client Fax Server Can be a fax client File Server Supported, except for DFSR Microsoft Windows SharePoint® Services Server Not supported Print Server Can print to another server Remote Authentication Dial-In User Service (RADIUS) Server Removable Storage, formerly Media Services Rights Management Services (RMS) Server Can participate as a client Routing and Remote Access Server Can participate in a virtual private NW (VPN) but cannot host or manage Terminal server Partial Support, but app execution and session directory are not supported Universal Description, Discovery and Integration (UDDI) Windows Deployment Services Hyper-V (Built-In Virtualization Engine) Can leverage other Hypervisor Itanium als Application Server ausgelegt! [Rev. # or date] – HP Restricted

23    Agenda Intro zu 64-Bit Computing
3/28/2017 8:11 PM Agenda  Intro zu 64-Bit Computing Intro zu x64 und Itanium Prozessor Architektur Unterschiede der 64-Bit Versionen in Windows Server 2008 32-Bit Apps in 64-Bit Windows Einsatzszenarien Zusammenfassung   ©2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

24 32-Bit App Kompatibilität in WOW64
[Course Title] [Module Title] 32-Bit App Kompatibilität in WOW64 Übersicht zu 32-Bit Apps auf 64-Bit OS Kompatibilitätsfragen : Haupt Beschränkung: alle Kernel Level Programme müssen nativ 64-Bit sein Beispiel: NIC Drivers, Antivirus Agents, Disk-Defrag Tools (für Server heute meist kein Problem mehr) 64-bit Kernel-Mode Treiber müssen digital signiert sein Andere Herausforderungen: 32-Bit in-process COM Komponenten (DLLs) nicht in 64-Bit Programmen erlaubt Entweder als out-of-process implementieren, oder durch native 64-Bit Version ersetzen 16-bit DOS und Windows (Win16) Applikationen sind NICHT auf Windows x64 lauffähig da NTVDM entfernt wurde [Rev. # or date] – HP Restricted

25 32-Bit App Kompatibilität in WOW64
[Course Title] [Module Title] 32-Bit App Kompatibilität in WOW64 Folder Redirection: Trennung von 32-Bit Programm- und System Dateien Normalerweise kein Problem für 32-Bit Apps, da Umlenkung komplett durch WOW64 gehandhabt wird "Program Files (x86)" Folder keine echte Umlenkung – wird nur als default Pfad bei Installation von 32-Bit Apps verwendet 25 [Rev. # or date] – HP Restricted

26 32-Bit App Kompatibilität in WOW64
[Course Title] [Module Title] 32-Bit App Kompatibilität in WOW64 Registry Redirection: Trennung der "Software" Node für 32-bit Apps in der Windows Registry Auch hier in der Regel kein Problem für 32-Bit Apps, da von WOW64 verwaltet Erlaubt Registry Keys für 32-Bit und 64-Bit Versionen der gleichen Applikation 26 [Rev. # or date] – HP Restricted

27 32-bit vs. 64-bit App Performance
[Course Title] [Module Title] 32-bit vs. 64-bit App Performance 64-Bit macht nicht alles automatisch schneller! Aber, falls die Applikation schon heute an Speichergrenzen stößt, werden die Vorteile schnell sichtbar Beispiel: .NET Web-Applications (CachePerf testapp) 1,000  Unique Searches  10,000 with Windows .NET 2.0 Worker-Process: 32-bit 64-bit 32-bit 64-bit Source: [Rev. # or date] – HP Restricted

28 32-bit vs. 64-bit App Performance
[Course Title] [Module Title] 32-bit vs. 64-bit App Performance Beispiel 2: AD Performance – hier spielt die Cache-Limitierung einer große Rolle… AD Cache Limitierung: Gesamtleistung hängt stark von der Datenmenge der AD Datenbank ab, die der LSASS Prozess (AD) im Speicher cachen kann… Operating System of DC standard LSASS cache (max) with /3GB Boot.ini switch Windows 2000 (32-bit)* 0.5 GB 1 GB Windows 2003/8 (32-bit) 1.5 GB 2.6 GB Windows 2003/8 x64 8 TB N/A * /3GB switch only available in Advanced Server Edition 28 [Rev. # or date] – HP Restricted

29 32-bit vs. 64-bit App Performance
[Course Title] [Module Title] 32-bit vs. 64-bit App Performance Noch Beispiel 2: LDAP Queries an Active Directory DCs auf 32-Bit Windows vs. 64-Bit Windows mit 10 GB AD Datenbank x64 System: 2 x 2.2 GHz AMD Opteron, 14 GB RAM x86 System: 2 x 2.4 GHz Xeon, 4 GB RAM System Avg query time Avg entries touched Avg entries / sec x64 25,422 ms 1,039,281 41,186 x86 *300,016 ms 374,692 1,249 8,224 ms 213,336 25,941 59,951 ms 3,560 Query1: touches as many objects as possible (1 Million) Query2: touches approx. 200k objects * Query on x86 32-bit DC exceeded LDAP policy limit for query duration (300 ms) 29 [Rev. # or date] – HP Restricted

30     Agenda Intro zu 64-Bit Computing
3/28/2017 8:11 PM Agenda  Intro zu 64-Bit Computing Intro zu x64 und Itanium Prozessor Architektur Unterschiede der 64-Bit Versionen in Windows Server 2008 32-Bit Apps in 64-Bit Windows Einsatzszenarien Zusammenfassung    ©2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

31 [Course Title] [Module Title] Paths to 64-bit Windows Many of today’s server install base still purely 32-bit, but many are End-Of-Life After 2005, most new server shipments have combined x64 hardware with 32-bit Windows  proliferation of x64 hardware will happen automatically Using Windows x64, companies will start combining 32-bit and 64-bit apps on the same system Itanium to be leveraged for most demanding applications 32-bit Applications 32-bit 32-bit x64 Itanium x64 Windows Server OS 32-bit 32-bit x64 x64 Itanium Device Drivers 32-bit 32-bit x64 x64 Itanium 32-bit x64 x64 x64 Itanium Server Hardware Pure 32-bit Stack Pure 64-bit Stack [Rev. # or date] – HP Restricted

32 Microsoft committed zu x64 und Itanium
Zukunft von x64 und Itanium bei Microsoft ? Microsoft 64-Bit Software and Prozessor Roadmap (Stand 02/2006) Source: Directions on Microsoft Microsoft committed zu x64 und Itanium

33 Übersicht der 64-bit Windows Einsatzszenarien
[Course Title] [Module Title] Übersicht der 64-bit Windows Einsatzszenarien Application oder Service Vorteil durch 64-Bit Windows SQL Database Server Allows large databases to be fully cached in memory, dramatically improving SQL query performance. Active Directory Domain Controller The increased virtual address space allows large AD databases to be fully cached into memory, dramatically improving LDAP query performance IIS Web Server Increases the number of application pools per web-servers and the virtual address space available per application pool. Results in better performance and better mean time between application and Web service recycling, thereby increasing overall website availability. SharePoint Portal Server SharePoint heavily relies on IIS and thus gains similar benefits when hosted on a 64-bit OS. Terminal Server More virtual kernel address space for the OS gives the ability to handle many more users per Terminal Server. Exchange Server More addressable memory reduces the problem with fragmentation of virtual memory and allows the Exchange Store to cache more mailbox data per user. This results in fewer I/O operations to disk which significantly increases performance. Virtual Server / Hyper-V Larger kernel address space allows better scaling to support more VMs per server, allowing a higher degree of consolidation. More virtual address space per VM allows increased performance for VMs themselves. [Rev. # or date] – HP Restricted

34 Spezieller Use-Case: Server Virtualisierung
[Course Title] [Module Title] Spezieller Use-Case: Server Virtualisierung Allgemeiner Vorteil von 64-Bit Computing für Virtualisierung: Vergrößerter Kernel Adressraum erlaubt die Unterstützung von mehr VMs pro Server, und somit einer erhöhte Konsolidierungsdichte. Mehr Virtueller Adressraum pro VM verspricht erhöhte Leistung der VMs selber. [Rev. # or date] – HP Restricted

35 Spezieller Use-Case: Server Virtualisierung
[Course Title] [Module Title] Spezieller Use-Case: Server Virtualisierung Microsofts Server Virtualisierungs Lösungen Virtual Server 2005 R2 x64 Edition nutzt Vorteile der x64 Architektur aus Nachteil von VS2005: unterstützt keine 64-bit Guests Windows Server 2008 mit eingebauter Virtualisierungs Lösung (Hyper-V) baut voll auf x64 CPUs Hyper-V unterstützt 64-bit Guests Lizensierung von Datacenter Edition: erlaubt unlimitierte Anzahl von VMs auf Windows Server Datacenter Edition (wie Windows Server 2003 R2) [Rev. # or date] – HP Restricted

36 Special Use-Case: Server Virtualization
[Course Title] [Module Title] Special Use-Case: Server Virtualization VMware: Seit Okt 2006: VMware Infrastructure 3.x hat volle Unterstützung für 64-bit Guests HP Virtual Machines Die Virtualisierungs-Lösung für Integrity/Itanium Multi-OS capabilities: Support von HP Integrity Virtual Machines Guests mit Windows (64-bit Windows Itanium Guests) Windows and Linux Support auch fuer HP Integrity Essentials Capacity Advisor and Virtualization Manager (neben HP-UX) Serviceguard Support für Fail-Over von Windows Guests (VM fail-over) Info: Windows für Itanium IA64 Lizensierung (Datacenter & Enterprise Edition) ist wie bei Windows Server 2003 x64 R2 [Rev. # or date] – HP Restricted

37 Haupt-Workloads für 64-bit Windows Server
[Course Title] [Module Title] Haupt-Workloads für 64-bit Windows Server Database Especially: OLTP, OLAP, Data Warehouse, Business Intelligence (Itanium / x64) Business Applications Especially: ERP, SCM, CRM, and custom LOB (Itanium / x64) Terminal Services Especially: 32-bit client applications on x64 servers, Office (x64) Active Directory Especially data stores larger than 2 GB (x64) Web Serving (IIS 6.0) Improves reliability by reducing cache recycling (x64) Technical Computing Especially: HPC Clusters (x64) [Rev. # or date] – HP Restricted

38 Database on 64-bit Windows
Large databases lack sufficient memory address space on 32-bit systems, which limits performance and scalability Windows Server 2003 Itanium and x64 Editions relieve this problem by providing: nearly unlimited virtual memory address space (4000x larger) Even 32-bit databases benefit from the additional virtual memory, Support for more physical memory allows larger portions of the database to reside in RAM Case Study Problem Fortune 100 company needed to analyze ongoing effects to revenue caused by discounting, foreign exchange rates, etc. Data spanned 20 million historic price points and 14 million sales line items Relatively simple queries took 8 hours to process on 2-way 32-bit server Solution Windows Server 2003 x64 Edition with SQL Server Yukon on 4-way x64 server Impact: Query time reduced from 8 hours to 5 minutes

39 Business Applications on 64-bit Windows
As business applications grow, they frequently need both greater processing power and more memory In a 32-bit environment, this typically causes I/O constraints and limits the number of end-users that can be supported Windows Server 2003 Itanium and x64 Editions relieve this problem by providing: nearly unlimited virtual memory address space (4000x larger) Up to 1 TB of physical memory Supports more users per server Case Study Problem Fortune 100 company needed to speed daily batch processing of their SAP implementation IT needed to make rapid upgrade without extensive disruption Solution Migrated 2-way 32-bit server to 4-way x64 server running Windows Server 2003 x64 and x64 version of SAP R/3 Impact: Batch processing times reduced by 67% (from 180 minutes to 60 minutes)

40 [Course Title] [Module Title] Terminal Services on x64 Terminal Services deployments are limited by available kernel address space on 32-bit systems This effectively caps the number of users that can be supported, regardless of how much memory or CPUs that are added Windows Server 2003 x64 Editions relieve this problem by providing larger kernel address space 170x larger PTE 272x larger paged pool memory 500x larger non-paged pool mem Benchmark Using identical 4-way, dual-core servers with 16 GB RAM, Windows Server 2003 x64 supported 170% more users than 32-bit Windows Server 2003 Workload simulates information workers using Microsoft Office [Rev. # or date] – HP Restricted

41 Web Serving with IIS 6.0 on x64
Case Study Problem Fortune 100 company with large international website found worker process uptimes were just 5 minutes during peak loads IT needed rapid solution that would preserve their investment in 32-bit ASP.net code Solution Migrated to Windows Server 2003 x64 running IIS 6.0 with 32-bit ASP.net Impact: Improved process uptimes from 5 minutes to several weeks No code changes to ASP.net applications required Web servers increasingly host large, distributed applications that place extensive demands on I/O Over time, worker processes run out of virtual address space in a 32-bit environment, forcing cache to recycle End-user experiences delays and/or errors Windows Server 2003 x64 with IIS 6.0 dramatically reduces cache recycling for large web applications, improving overall reliability and end-user experience

42 Active Directory on x64 Active Directory data stores larger than 2GB (roughly 10k objects) must be stored on disk in 32-bit environments, significantly impacting performance Additional servers may be required to meet same SLAs Windows Server 2003 x64 Editions allow large Active Directory data stores to be entirely resident in RAM, dramatically improving performance Improved I/O buffering Reduced load on I/O subsystem Faster replication of changes Case Study Large multinational dedicated nine Active Directory domain controllers to their Exchange 2003 implementation to support rich query load Scale out required to maintain desired performance levels Company migrated to Windows Server 2003 x64 Editions Impact: Consolidated 9 domain controllers down to 4 with equal or better performance

43 Technical Computing on x64
Technical Computing, and High-Performance Computing Clusters (HPCC) in particular, is both memory-intensive and computationally intensive The memory barriers inherent with 32-bit systems limit the performance of HPC clusters Windows Server 2003 x64 Editions relieve this problem by providing nearly unlimited virtual address space Forms foundation for forthcoming Compute Cluster Edition Case Study Problem Fortune 100 company using 32-bit software to analyze portfolio risk unable to complete queries rapidly As assets outgrew 32-bit server capacity, data needed to be split and queries would take up to 40 hours to complete Solution Migrate existing 32-bit analysis software to Windows Server 2003 x64 Editions Impact: Query times reduced by 67% (from 40 hours to 13 hours)

44       Agenda Intro zu 64-Bit Computing
3/28/2017 8:11 PM Agenda  Intro zu 64-Bit Computing Intro zu x64 und Itanium Prozessor Architektur Unterschiede der 64-Bit Versionen in Windows Server 2008 32-Bit Apps in 64-Bit Windows Einsatzszenarien Zusammenfassung      ©2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

45 Key Take Aways 64-Bit ist Hier und Heute
Enorme Performance Vorteile für Programme die heute schon am Speicherlimit arbeiten (auch für 32-Bit Apps auf x64) Itanium2 spielt in einer anderen Liga als x64 x64 = mainstream to mid-range Itanium2 = mid-range to high end Schon jetzt vorbereiten auf die Welle der nächsten 64-bit Applikationen (wie Exchange 2007) Die meisten Infrastruktur-Rollen können ohne weiteres auf 64-Bit migriert werden (z.B. AD, File-Services) Es ist wichtig, die „kleinen“ Unterschiede zwischen 32-Bit und 64-Bit OS für den reibungslosen Betrieb zu kennen…

46 Windows Server 2008 weitere Ressourcen
3/28/2017 8:11 PM Windows Server 2008 weitere Ressourcen Windows Server 2008 Tech Center Windows Server 2008 Webcasts: Windows Server 2008 Produktseite: Microsoft Virtualization: © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

47 Ask the Experts Wir freuen uns auf Ihre Fragen: Technische Experten stehen Ihnen während der gesamten Veranstaltung in der Haupthalle zur Verfügung.

48 3/28/2017 8:11 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

49 demo { demo title } Name Title Group 3/28/2017 8:11 PM
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.