UNC309 - Getting the Most out of Microsoft Exchange Server 2010: Performance and Scalability
Download as PPTX, PDF2 likes1,845 views
The document outlines performance and scalability guidelines for Exchange Server 2010, emphasizing strategic choices between scaling out and scaling up server configurations. Recommendations include specific hardware configurations, role-specific details on memory and processor requirements, and virtualization considerations to optimize performance. It also highlights tools for planning and sizing, ensuring users understand the balancing act between resource allocation and operational efficiency.
UNC309 - Getting the Most out of Microsoft Exchange Server 2010: Performance and Scalability
- 2. Getting the most out of Exchange Server 2010: Performance and ScalabilityJeff MealiffeSenior Development LeadMicrosoft CorporationSession Code: UNC309
- 3. AgendaHigh-level product direction for scaleGuidelines and ratiosRole specific detailsVirtualization considerationsToolkit for planning and sizing
- 4. Product Direction For Scale
- 5. Scale Out vs. Scale UpScale out is a strategic choice made by the product groupScale out provides the following at low cost:Large mailboxesHigh availabilityRich feature setScaling up increases risk that an outage or failure affects more usersScaling up usually costs more, and can force feature decisions due to hardware choicesConsider all factors in the equation, particularly storage
- 6. Scale Up OptionsMultiple Role Servers (“brick” deployments)Likely the best option for big hardware (> 2 socket) – best hardware utilization overallBe aware of recommendations for max processor & memoryVirtualizationEvaluate whether potential added complexity & monitoring challenges make this a winSingle roleProduct not engineered for single role high scale (> 2 socket)Extreme caution necessary – validate carefully in a test lab
- 7. Supported vs. RecommendedSupported usually means well testedSupport statements define strict boundariesRecommendations define the “best case” or the state that we want our customers to achieveUnderstand risks of going outside of recommendations or support boundaries
- 9. Processor Core ScalabilitySingle Role ServersRecommend a 2-socket platform4-core processors = 8 total cores6-core processors = 12 total coresExpect diminishing returns moving to 16+ cores on >= 4 socket platformKnown issues updating memory across coresNot Non-Uniform Memory Access (NUMA)-aware or optimized for scale around data localityCode can take longer to execute; transaction costs riseMultiple Role ServersRecommend 24 cores maximum for high-scale “Enterprise Multiple Role Server”Multiple processes from different roles help us scale betterHyperthreadingDisable on production Exchange serversCauses monitoring and capacity planning challenges
- 10. Role Ratio GuidelinesProcessor core ratiosCAS : Mailbox= 3 : 4HUB : Mailbox= 1 : 7 (no A/V on Hub)= 1 : 5 (with A/V Hub)GC : Mailbox= 1 : 4 (32-bit GC)= 1 : 8 (64-bit GC)
- 11. Processor and Memory Config
- 12. Network Load BalancingExchange 2010 requires load balanced CAS for internal connectionsConsider HA needsSize for connection count spikesWindows Network Load Balancing (NLB)Not recommended above 8 nodesHardware Load BalancerRecommended for larger environmentsMultiple Role Server High Availability (HA) scenarios
- 14. Mailbox RoleGeneral guidanceI/O reduced by 70% from Exchange Server 2007Improved performance for SATA (Tier 2 class) disksTwo socket platform still optimalStorage performance improvements prioritized over processor scale improvements – larger TCO advantageHigh availability improvements affect sizingSizing must account for failure scenariosUse 4 – 12 total cores for Mailbox16 core not expected to scale well but ok to deploy – consider TCO4GB RAM w/3-30MB per mailbox recommended depending on profileSize and prepare disks correctlyUse Exchange Storage Calculator
- 15. Mailbox RoleMemory sizingDesign servers with large quantities of memoryDeep checkpoint depth + 32KB pages allow E2010 to benefit from larger memory configurations than E2K7More database cache results in less IOPS/mailbox
- 16. Mailbox RoleHigh availability sizingSize for active users on DAG nodes, assuming the possibility of double failuresDo not overcommit resourcesSpread node failure across all available nodes not one or twoDistribute database (DB) copies across nodes in a matrixImproved DB seed/log shipping performance across WANLog Shipping compression/encryption (opt in)New log shipping architecture (Transport Control Protocol (TCP) socket based as opposed to Server Message Block (SMB), connection/DB)Improved high latency capabilityUse multiple 1GB networks or 10GB networkImproves LAN re-seed/log replication queue drain performanceEspecially with large servers and/or large databases
- 17. Client Access Server RoleConnection scalability changesOutlook ClientsOutlook ClientsExchange 2007(1 connection == 1 session, 64K RPC Context handle limit)64K connections / MBX serverExchange CAS ArrayExchange 2010(1 connections != 1 session, 250K RPC Context handle limit on MBX)1 MBX session :1 client sessionMBXMBX1 connection :1 client session1 CAS session :1 client session100 shared connections
- 18. Client Access Server RoleGeneral guidanceHardware requirements have increased vs. Exchange 2007“Pay to play” for additional features and services (RPC Client Access Service, Address Book Service, Remote Powershell, etc.)Possible to keep CAS count constant from 2007 to 2010, with hardware refreshUse 4 to 12 coresRecommend larger of 8GB RAM or 2 GB RAM/coreCAS : Mailbox = 3 : 4 Cores
- 19. Hub Transport RoleGeneral guidanceIncreased workload in Exchange 2010Additional CPU required when compared to Exchange 2007Not significant enough to result in a core ratio changeUse 4-12 cores4-8 GB of RAM recommendedMore than 8GB is not shown to improve TCO or scaleUse battery-backed write cache disk controllerDisk I/O can be a bottleneck on an un-tuned HubLog I/O becomes virtually free with a BBWC controller
- 20. Hub Transport RoleQueue database changesESE changes:ESE page size increased from 8KB to 32KBESE database page compressionIntrinsic long value record storageESE version store maintenanceDB cache size increased from 128MB to 1GBCheckpoint depth increased from 20MB to 512MBLogging buffer size increased from 512KB to 5MBWith transport dumpster changes and ESE improvements, transport IOPS requirements have been reduced by more than 50%
- 21. Unified Messaging RoleGeneral guidanceUse 8 core for Voice Mail PreviewCPU-intensive workload4 core recommended for other scenarios4-8 GB of RAM recommendedMore than 8GB is not shown to improve TCO or scaleNot recommended combining with other rolesAudio quality can be affectedEnsure low latency to mailbox servers associated with UM-enabled accounts
- 22. Multiple Role Server General guidanceMailbox, CAS, and Hub Transport roles onlyAvailable solution for high core configurationsHalf of cores for Mailbox, half for CAS+HubUse 8-24 cores8GB RAM plus 3-30MB/mailbox recommended (follow mailbox database cache sizing guidance)
- 23. Multiple Role ServerDeployment scenariosSimple unit of scale (brick) modelEach multi-role server represents a building blockServers with on-board SATA storage (10-16 disks) are optimalSmall organization/branch office – server consolidationMinimize the number of physical servers, operating system instances, and Exchange server instances to manageRisk mitigation scenarios Policies that limit the amount of mailboxes per server
- 25. Support GuidelinesTechNet is the single source: http://technet.microsoft.com/en-us/library/cc794548.aspxSVVP Support Policy Wizard is a great tool:http://www.windowsservercatalog.com/svvp.aspx?svvppage=svvpwizard.htmAlways confirm SPW results with our TechNet articleCheck back for updatesClarifications published frequently
- 26. Supportability Quick ReferenceSupportedRoot: Hyper-V or SVVPGuest:Exchange 2010Windows 2008 SP2 or R2Mailbox, Client Access, Hub Transport, Edge rolesMeets basic Exchange system requirementsStorage is fixed VHD, SCSI pass through, or iSCSINot SupportedCombination of Exchange Mailbox HA and hypervisor-based clustering or migration technologiesSnapshots, differencing/delta disksVSS backup of root for passthrough disks or iSCSI disks connected to initiator in guestUnified Messaging roleVirtual/logical proc ratio greater than 2:1Applications running in root partition
- 27. Deployment RecommendationsVirtualization isn’t freeHypervisor adds processor overhead, must account for this when sizing - ~12% in our Exchange 2010 testsWorkload costs rise as well, though this is more difficult to characterizeVirtualization doesn’t change Exchange design requirements from an application perspectiveDesign for Performance, Reliability and Capacity (MBX/Hub/Edge)Design for Usage Profiles (CAS/MBX)Design for Message Profiles (Hub/Edge)
- 28. Exchange 2010 TestingTypical 16-core deploymentGoal: Examine Exchange performance on Hyper-V in a typical deployment scenarioTest configuration:HP ProLiant BL680 G5, 4 x Quad-Core Intel Xeon E7340Root: 16 core host, Windows 2008 R2 (build 7100)Guests: 4 VMs (1 CAS, 1 Hub, 2 Mailbox), Exchange 2010 DF7 (582.10)Mailbox 1 on Windows 2008 RTM, Mailbox 2 on Windows 2008 R24,000 users per mailbox serverLoadgen, 75% Outlook 2007 Cached Heavy + 25% OWA (modified enterprise script) + 10% default EAS workloadObservations:Logical processor guest runtime higher with 2008 RTM guest vs. 2008 R2 (~13%)Acceptable performance across all rolesHub CPU 52.3%, CAS CPU 33.4%MBX CPU 53.3%, RPC Averaged Latency 6.5ms, RPC Operations/sec 1818
- 29. Points To ConsiderAccuracy of Perfmon counters in a Guest OS might be a concern for monitoringCPU cycles in a VM are relative to the CPU slices provided from the virtualization layerMay skew resultsInvestigating the impact on production monitoringComprehensive comparison of physical resources and application consumption is difficult to achieveApplication counters are only available in the Guest OSRoot OS only provides view of resources it owns and Hyper-V counters
- 30. Toolkit For Planning & Sizing
- 31. Capacity Planning ToolsProfilingExchange Profile Analyzer 2010 (EPA)Performance Monitor (Perfmon)SizingExchange Server 2010 Storage CalculatorValidationJetstress 2010Exchange Load Generator 2010 “Loadgen”
- 32. Exchange Profile Analyzer 2010Generates statistical profile of user actionsMessages sent and received/dayRule countsItem size and countsInputsCrawls mailboxes with MAPI (previously DAV) OWA log analysis tool and “summarizer”Accuracy somewhat dependent on how users manage their mailboxAvailability planned for Q3CY10Version that works with Exchange 2003 & 2007 available here: http://tinyurl.com/233by6
- 33. Storage Calculator 2010Follows Product Group recommendations on:StorageMemoryMailbox sizingGoal of the calculator is to output:I/O requirements Capacity requirements Logical user number (LUN) designAvailable today via the Exchange team blog: http://msexchangeteam.com/
- 34. Jetstress 2010Exchange I/O simulatorUses Jet (ESE) database engineAnalyzes server I/O performance for Exchange requirementsWhat can Jetstress be used for?Storage performance validationStorage reliability testingEnd-to-end testing of storage componentsWhat can’t Jetstress be used for?Validation of client experienceIntegration testing with third party software solutionsAvailability of 2010 version planned for December 2009, will be announced on Exchange team blog: http://msexchangeteam.com/
- 35. Jetstress 2010What’s newUpdated with Exchange 2010 Mailbox I/O ProfileThis profile is not yet final and is subject to change between now and Exchange 2010 releaseDatabase duplication is now multi-castDramatically reduces the time to prepare databases for testingNow using MSExchange Database I/O counters for I/O measurementAllows placing databases and logs on the same volumeLog replication I/O is simulated based on Exchange 2010 HA architectureBackground Database Maintenance (Checksum) is now simulated
- 36. Exchange Load Generator 2010The only supported multi-protocol load generator for ExchangeReplaces Loadsim and ESPWindows UI interface as well as a command-line interfaceBoth task-based and scripted simulation modesConsumed both internally at Microsoft and externallyExisting modules include: Outlook 2003/2007 (online and cached), Post Office Protocol (POP), Internet Message Access Protocol (IMAP), Simple Mail Transfer Protocol (SMTP), OWA, ActiveSync… others in developmentAvailability planned for December 2009, use beta until then:http://tinyurl.com/yhvpwbf (32-bit)http://tinyurl.com/yk5vfl7 (64-bit)
- 37. Exchange Load Generator 2010What’s newRequires Vista, Windows 7 or Windows 2008 OS (SP2/R2)No longer requires Exchange Management ToolsActiveSync ModuleDynamic mail generatorNo need for message files, available in 5 languages, supports attachmentsNSPI connections
- 38. Tools Process FlowUserProfileExchange Load GeneratorMailflow& Other StatsExchange Profile AnalyzerUserProfileExchange Storage CalculatorIOPSPerformance MonitorExchange Jetstress
- 39. Key TakeawaysExchange continues to reduce I/O requirements, reducing overall system TCONew features in Exchange 2010 may require additional hardware resources, server count increases can be minimizedVirtualization is a great way to take advantage of underutilized hardwareTake advantage of the planning & testing toolset for successful deployments
- 40. Related ContentRequired SlideSpeakers, please list the Breakout Sessions, TLC Interactive Theaters and Labs that are related to your session.UNC301– Microsoft Exchange Server 2010 Upgrade and Coexistence with Exchange Server 2007 and 2003UNC307 – Microsoft Exchange Server 2010 High AvailabilityUNC314 – Microsoft Exchange Server 2010 Storage ArchitectureUNC315 – Microsoft Exchange Server 2010 Unified MessagingUNC01-IS– Microsoft Exchange Server 2010 Archiving Q&AUNC06-IS – Site Resilience in Microsoft Exchange Server 2010UNC03-IS – Microsoft Exchange Server Virtualisation: Does It Make Sense?
- 41. UNC Track Call to Action!Learn More!Related Content at TechEd on “Related Content” SlideAttend in-person or consume post-event at TechEd OnlineCheck out learning/training resources at Microsoft TechNetExchange Server and Office Communications ServerCheck out Exchange Server 2010 atVirtual Launch Experience (VLE) at thenewefficiency.comTry It Out!Download the Exchange Server 2010 TrialTake a simple Web-based test drive of UC solutions through the 60-Day Virtual Experience
- 42. Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!
- 45. Required Slide© 2009 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.
Editor's Notes
- #10: Disable HT