Anith Gopal

Windows Server 2008 R2 represents the latest evolution of the Windows Server operating system and corresponding support for high-end hardware systems with large numbers of microprocessors.  The 64-bit versions of Windows 7 and Windows Server 2008 R2 support more than 64 Logical Processors (LP) on a single computer. Microsoft has tested R2 with 256 processor systems; the largest systems available at present.  New commodity computer systems will soon appear that leverage NUMA architectures.  A system with 4 CPU sockets, 8 processor-cores per socket and with Simultaneous Multi-Threading (SMT) enabled per core, will readily achieve 64 Logical Processors.   R2 features enhanced support of Non-Uniform Memory Access (NUMA) computer architectures along with new User-Mode Thread Scheduling (UMS) technology.    UMS enables custom thread-level scheduling within your own application.   For certain categories of computing scenarios, this avoids the overhead of kernel transitions and context switching.  New API’s are available for both NUMA and UMS technologies.   Many high-end multi-core server-class software solutions may now be developed with NUMA and/or UMS integration in order to achieve linear performance scaling.  Parallel Computing and High Performance Computing solution developers may find NUMA awareness essential for performance scalability.

Trigger-Started Services are new with Windows Server 2008 R2 and Windows 7.   Before, services were typically started at system boot time and ran until system shutdown.   Now, services can specify start and stop conditions (triggers). Common usage scenarios include: Device class arrival and removal Example: “Bthserv” starting on bluetooth device class arrival IP address arrival and removel Example: “Lmhosts” start on first and stop on last IP address availability Firewall port event Example: “Browser” open of NS and DGM ports Domain join and unjoin Example: “W32Time” start on join, stop on unjoin Custom ETW event Example:  “AppID” start when SRP enabled Trigger meta-data is stored in the service registry key.   You can use the “sc qtriggerinfo” command to view service triggers