Exchange Server 2013 Performance Recommendations

Applies to: Exchange Server 2013

Exchange Server 2013 performance tuning and troubleshooting is most effective when your environment has been properly sized and planned. While Exchange 2013 was designed to simplify the underlying resource infrastructure, it can still consume a large amount of system resources, such as memory, storage capacity, and CPU capacity.

The articles in this section were written by the Exchange performance team. They contain expertise from the Exchange product group, as well as best practices learned from customer support cases. The goal of these articles is to help you understand the impact of changes introduced in Exchange 2013, and the importance of appropriately sizing your Exchange 2013 infrastructure. We've also included recommended optimizations and guidance on identifying performance issues.

Architectural Changes in Exchange 2013 and other Resources

The architectural changes in Exchange 2013 are already documented on TechNet and in the Exchange Team Blog. We'll first touch upon a few high level changes you should consider in order to better understand performance cost and sizing. Then, below, we've included a list of recommended references to provide further context and background in these important areas.

Note

Please see Exchange 2013 virtualization for performance optimization guidance about deploying Exchange Server 2013 in a virtualized environment.

In Exchange 2013, the Client Access server role is a stateless proxy server. Now the Client Access server role's primary responsibility is to authenticate incoming requests and then proxy each request to the appropriate Mailbox server, the one hosting the active copy of the user mailbox. This means it's no longer necessary to configure affinity between the Client Access server and load balancer for specific protocols.

Another noteworthy change in Exchange 2013 is in the Information Store. The Information Store now consists of two kinds of processes: host and worker. Each database instance is associated with its own Microsoft.Exchange.Store.Worker.exe process. This allows for better isolation of problematic database issues, and can reduce the performance impact of a database problem to just the one worker instance for that database.

The Microsoft Exchange Replication service is responsible for all high availability services related to the Mailbox Server role. This replication service hosts the Active Manager component, which is responsible for monitoring failures and taking corrective actions.

A great post on architectural changes, including the impact to re-sizing an Exchange 2013 environment from earlier versions, can be found in Exchange 2013 Server Role Architecture.

More about Exchange 2013 architectural changes, and background information on other relevant areas, can be found in the following:

Exchange Server 2013 Architecture

Plan it the right way: Exchange Server 2013 sizing scenarios

Monitoring and Tuning Microsoft Exchange Server 2013 Performance

Implementing Exchange Server 2013: (01) Upgrade and Deploy Exchange Server 2013

Implementing Exchange Server 2013: (02) Plan It the Right Way: Exchange Server 2013 Sizing

Implementing Exchange Server 2013: (03) Exchange Server 2013 Virtualization Best Practices

Implementing Exchange Server 2013: (04) Exchange Architecture: High Availability and Site Resilience

Implementing Exchange Server 2013: (05) Outlook Connectivity

The Preferred Architecture

Exchange 2013 Client Access Server Role

Exchange Server 2013 Virtualization Best Practices

Load balancing

Exchange Server Updates: build numbers and release dates

Release notes for Exchange 2013

Updates for Exchange 2013

ASP.NET Thread Usage on IIS 7.5, IIS 7.0, and IIS 6.0