Managing Your Cross-Platform Data Keynote: The Power of 64

Speaker Name HereDate

The 32-bit ChallengeToday, customers are experiencing unprecedented challenges in their computing environment

Increased complexity in mixed IT environmentsEver increasing user countsPower, space and heat restrictions

It is becoming increasingly difficult to sustain Mission-Critical databases on 32-bit architectures

Difficulty in scaling to handle increasing database sizesDifficulty in managing large concurrent user counts

There is a limited future for 32-bit processors, 32-bit Operating Systems, and 32 bit databases

All current and future hardware and software development is oriented towards 64-bit platforms

The 64-bit SolutionMicrosoft and Intel have solved these problems by extending their platforms to provide advanced 64-bit architectures

Dual-Core Intel® Xeon® processor-based systems offers hybrid 32-bit/64-bit capabilities that make the transition to 64-bit processing easy

Intel Itanium® 2 processor-based systems offers high-end performance capabilities for the most demanding and mission-critical corporate databases

Microsoft offers Windows Server 2003 editions for both the Xeon® and Itanium® 2 architectures

The 64-bit SolutionBoth SQL Server 2005 and Oracle 10g offer 64-bit versions for both the Xeon® and Itanium® 2 architectures

Compared to 32-bit database versions (Windows/UNIX/Linux), the 64-bit Windows versions of both SQL Server 2005 and Oracle 10g provide outstanding performance

When compared to 64-bit database versions on UNIX/Linux, the 64-bit Windows versions of both SQL Server 2005 and Oracle 10g offer competitive performance, even superior performance in some scenarios

Windows Server 2003 Family32-bitx86

64-bitx64

64-bit Itanium

Up to 32-way,64 GB RAM

Up to 64-way,1 TB RAM

Up to 64-way,

1 TB RAM

Up to 8-way,64 GB RAM

Up to 8-way,1 TB RAM

Up to 8-way,1 TB RAM

Up to 4-way,4 GB RAM

Up to 4-way,32 GB RAM n/a

Up to 2-way,2 GB RAM n/a n/a

Windows Architecture: Thread Model

On Windows, both SQL Server 2005 and Oracle 10g are implemented as single operating system processes per instanceThis is distinctly different than UNIX/Linux ports of Oracle Database 10g, where there are multiple background processesTypical Oracle “processes” such as PMON and LGWR have been converted to native Windows threads running in the single large Oracle process The Windows thread model is generally beneficial to performance, but also causes some memory implementation limitations under 32-bit Windows

32-bit Addressing32-bit processors have address registers that are 32-bits wide (can address up to 4GB RAM)

Each individual process gets its own virtual address space that can be up to 4GB

This virtual address space is divided – system and user space, by default 2 GB each

The user space can be extended to 3 GB with the 4GT feature

/3GB flag = 4GB Tuning Feature – reduces system space to 1GB, allowing 3GB for user space

Add to boot.ini file and reboot to take effect

Windows Threads And MemoryOracle or SQL Server process

2GB or

3GB total

Code

Oracle SGA or SQL Server Buffer Cache + Procedure

Cache

SGA contains db buffers, log buffers shared pool, other memory allocationsEach thread consists of PGA, stack, other memory allocationsBackground and foreground

threads

For Kernel 1-2GB

32-bit Systems With PAE And AWEPAE - Physical Address Extension

Allows 36-bit memory addressing

Allows the IA32 processor to address up to 64GB of physical RAM

Add /PAE switch in the boot.ini file and reboot server

AWE – Address Windowing ExtensionAWE – a set of APIs that allow programs to address memory locations outside of their 4GB virtual addressing range

With AWE programs reserve memory as non-paged (will not page out)

These methods add a translation layer to memory access – slower than direct memory access

SGA minus db buffers

Code

RES

T O

F

RA

M

For O/S, other apps

3GBwith AWE

12-60 GB

Window on dbbuffers in AWE

mem

Extended memoryavailable for db

buffers via AWE calls

Memory from AWE calls used for db buffers only. VLM memory can be tuned for 12 GB – 60 GB of database buffers. Requires /PAE flag plus ~ 1 GB AWE Window in low memory (Oracle only)

Oracle operating system process. Limited to 3GB of address space (with /3GB flag). Note that after subtracting AWE overhead, memory for non-db buffer components of the SGA is only 1-2 GB.

1 GB

For Kernel

32-bit: VLM Support

Performance Implications Of 32-bit Memory

Memory split into two parts is not as efficient as memory in one segment

Overhead is introduced, memory access is substantially slower32-bit systems with 8 GB of RAM may not perform much better than systems with 4 GB of RAM

Memory above 4 GB can only be used for Buffer cache (Oracle and SQL Server)

Buffer cache does not support user connections; all user connections must be supported from low memory (<= 3GB)AWE overhead may take up an additional 1 GB of low memory, leaving only 1-2 GB for managing user connectionsSQL Server connections are lightweight, so 4,000+ connections are possible, even with limited memoryHowever, Oracle connections require ~ 15-20 MB of memory, limiting concurrent connections to low 100s (Dedicated Server) – 2,000 (Shared Server)

Additional 64-bit Windows Advantages: Thread Model

Thread model benefitsFaster context switches

Decreased memory usage

Quicker connection times

Perceived as a more “native” implementation since it uses threads versus processes

No changes required for client applications

Can perform faster than Process model for CPU-intensive operations

Additional 64-bit Windows Advantages: Thread Tuning

Both CPU affinities and thread priorities can be set and manipulated via registry parameters on a thread-by-thread basisUser-thread support

Users may now run the database in user-thread mode, which employs database-scheduled fibers instead of O/S scheduled threads

For CPU intensive apps, this will provide a performance boost and reduce CPU utilization

Windows Server 64-bit Versions

Gradually replaces 32-bit Windows as mainstream offering

Suitable for all workloads

Well-suited for combining 32-bit and 64-bit software

Benefits from latest innovations such as multi-core, reduced power consumption and heat

Intended for the most demanding Database and LOB deployments on 8-way+

Designed for pure 64-bit software stacks

Optimized for high performance

x64 Server Optionsx64 hardware supports multiple configurations

Extends hardware investment by allowing gradual migration to 64-bit computing

Provides superior 32-bit performance and very good 64-bit performance

Server Hardware

Device Drivers

Windows Servers

Applications

32-bit Stack

64-bit StackHybrid Stack

x64

32-bit

32-bit

32-bit

x64

x64

x64

32-bitx64

x64

x64

x64

x64

Itanium Benefits For DatabasesLarger cache size

Fast Itanium® 2 on-die L3 cache up to 24 MBLess cache latency (fewer clock cycles needed)Databases benefit greatly with larger caches closer to the processorAllows for “bigger” systems

Better ParallelismBetter Instruction level parallelism (11 issues ports)More registers (264 registers supporting parallel instructions and reduce need for memory access)Improved Scalability of System Bus allowing for bigger systems

Improved Micro ArchitecturePredication removes delays caused by mispredicated branches

Scalability

Bre

ad

th o

f A

pp

licati

on

s

Versatile

Mainstream

64-bit x64

64-bit Itanium

Most Scalable

32-bit x86

Migration To 64-bit

Business Benefits Of 64-bit MigrationMeet increasing business demands

Allow more complex workloadsServe greater number of customersImprove response times

Increase cost effectivenessDo more work on the same budgetEnable server and database consolidationMake more efficient use of Datacenter resources

“Future proof” your database investmentAll development resources are being directed towards 64-bit platformsThe “tipping-point” for moving 64-bit processing into the mainstream has been reached

SummaryThe 32-bit architecture is no longer adequate to support the demanding workloads of Microsoft Windows databasesIntel offers Dual-Core Intel® Xeon® and Dual-Core Itanium® 2 processor-based server architectures for 64-bit processing, and Microsoft offers Windows Server 2003 for both architecturesDatabases on 64-bit versions of Microsoft Windows Server 2003 perform substantially better than their 32-bit counterparts

SQL Server 2005 and Oracle 10g scale better due to superior handling of Large Memory

Oracle 10g also benefits from unlimited user connectivity

On CPU-intensive tasks, 64-bit multi-threaded databases on MS Windows may perform better than 64-bit UNIX/Linux databasesThe Windows x64 Editions on the Dual-Core Intel® Xeon® server architecture offers a hybrid 32-bit/64-bit architecture that eases the transition to 64-bit computingThe Intel Itanium® 2 processor-based server architecture is optimized for high-performance databasesMigrating to 64-bit technology is a way to “future-proof” your database investment

Video

First American Title Insurance

© 2006 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.