When you have performance related issues and concerns that are the basic things to look for in exchange 2010?
Possible causes of poor performance ,
Performance issues may raise when mail server is sized wrong and unable to satisfy the current load, the basic counters, Memory, CPU, Disk averaged read write. The typical indication of poor performance , outlook popup indicates retrieval data from problem.ExcahngeServer.local etc..
What to look for?
Isolate if the issues is specific to one client or effecting more then one user.
Understand and investigate your CAS Servers , “CAS ARRAY”, remember when MAPI ( Outlook) client opens up MAPI request to connect to it’s own mailbox the, MAPI request will not directly go to Mail Box servers, it will go to your CAS server and CAS will talk to MBX server ( MAPI) behalf of requester.
Use your tool box and set of tools in there in E210. the most common one is Performance Troubleshooter.
I want to talk about MSExchangeIS\RPC Averaged Latency and the changes in the counter recommended thresholds.
in Exchange 2003 and 2007
|MSExchangeIS\RPC Averaged Latency < 10ms|
The value has changed as the business logic
|MSExchangeIS\RPC Averaged Latency < 250ms|
The new model in E210 Client MAPI request shown as below. The MAPI client ( Outlook) who want to connect to it’s mailbox database has to fallow below logic.
Outlook Client ( MAPI Users)---------(MAPI)------------> CAS ----------(MAPI)-----------MBX Server
MBX--------------(MAPI)------------->CAS----------(MAPI)---------->Outlook Client ( MAPI Users)
- Averaged Latency should be less than 250ms at all times……
- The generally-accepted warning threshold for MSExchangeIS\RPC Requests is less than 70 at all times…..
What would be considered as bottleneck ?
- Although store.exe has 500 threads in Exchange Server 2007 / 2010, consuming more than 70 at one time is evidence of a bottleneck.