Windows Server 2003 Necessary Information.ppt

Agenda Scaling: Scale-up and Scale-out Understanding resource bottlenecks on your server Scale-Up CPU, Memory, Disks, What we can expect from servers today What does this mean for Windows applications Databases Exchange Server File Server Terminal Servers Scale-Out Clones Partitioning Scale-Up and Scale-Out together Application example Sieble Enterprise Application Agenda Scale-up and Scale-out Scale-Up CPU, Memory, Disks What does this mean for Windows applications Scale-Out Clones Partitioning Scale-Up and Scale-Out together Application example Sieble Enterprise Application Scalable Systems Scale UP: grow by adding components to a single system Scale Out: grow by adding more systems Everything starts with understanding your computer Agenda Scale-up and Scale-out Scale-Up CPU, Memory, Disks What does this mean for Windows applications Scale-Out Clones Partitioning Scale-Up and Scale-Out together Application example Sieble Enterprise Application The Memory Hierarchy Locality REALLY matters CPU 2 Ghz, RAM at 5 MhzRAM is no longer random access Organizing the code gives 3x (or more) Organizing the data gives 3x (or more) Level latency (clocks) Registers 1 L1 2 L2 10 L3 30 Near RAM 100 Far RAM 300 32-bit Windows Virtual Address Space Memory Mapping Physical Address Extension for IA32 PAE required, if using 4GB physical memory Makes additional memory available to the OS Has no impact to applications Applications require AWE (see later) Enabling PAE Address Windowing Extension API’s Allows Applications to bypass the 4 GB limit Advantages of the AWE API’s Small API Set utilizing a windowing technique VirtualAlloc() with the MEM_PHYSICAL FLAG AllocateUserPhysicalPages() MapUserPhysicalPages() FreeUserPhysicalPages() AWE Mechanism Hot-Add Memory Requires Hardware and BIOS support SRAT ACPI 2.0 Reporting Memory at Post Memory Profiling Memsnap.exe takes a snapshot of all memory resources used by processes and writes them