Exchange 2016 starts the Exchange EAC Performance console interface

The Exchange EAC Performance console provides a number of performance counters for the EAC, which are present by default, except for states that are not displayed. We can use it to check how long it takes to authenticate the user, the server processes the request, and so on.

Today, simply say how to start the Performance console in the Exchange EAC. As a point of note, Exchange 2010, 2013, and 2016 apply this method, and other versions of the mini-series are not currently tested.

1. Log in to the Exchange server and Access %exchangeinstallpath%\v15\clientaccess\ecp\web.config;

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m00/71/7e/wkiol1xsnpljpk02aaozizff_l4509.jpg "height=" 519 "border=" 0 "/>

2. Edit the Web. config to locate ShowPerformanceConsole，编辑属性为true，默认是false ;

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/71/7e/wkiol1xsnpozwqebaauemyzavqa940.jpg "height=" 484 "border=" 0 "/>

3. Save and restart the IIS service;

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/71/81/wkiom1xsmujapkdsaagztxlhz_0448.jpg "height=" 257 "border=" 0 "/>

4. Login ECP;

No, it's like this.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m01/71/7e/wkiol1xsnpts9t8zaabthzuqtti315.jpg "height=" 198 "border=" 0 "/>

This is what happens when you start.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/71/7e/wkiol1xsnpxyl2u2aacczjdjom8252.jpg "height=" 243 "border=" 0 "/>

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/71/81/wkiom1xsmurbfycnaaedycucn_a325.jpg "height=" 312 "border=" 0 "/>

Specific performance parameters:

Request URL-The URL requested by the user;
Customer request Time (MS)-used in the total time of the request, which is measured by the client. This value ultimately applies to user-perceived performance;
Client network time (milliseconds)-time spent by the browser is sent, waiting for and receiving a response from the server;
UI Response (MS)-time is received by the browser to spend processing responses. This value measures the performance of the client UI code;
Server request time (milliseconds)-the total time spent processing requests on the server. However, this does not include requests that are sent or received during network time;
RBAC session-The number of RBAC sessions created during the request. A value of 1 means that a new session is created, and a value of 0 indicates that the cache session is used;
RBAC Session Delay Time (MS)-time spent in RBAC meetings during creation of requests;
RPC Request-The number of RPC operations required to execute;
RPC delay Time (MS)-time request during RPC operation spent;
LDAP request-The number of LDAP operations performed during the request;
LDAP latency Time (milliseconds)-time of the request during the LDAP operation of the flower;
Serialization-several times the Windows Communication Foundation [WCF] objects during serialization or deserialization of requests;
Serial time (milliseconds)-time spent in WCF serialization or request deserialization of an object in the process;
Run space-the number of Windows PowerShell run space created during this request. A value of 1 indicates that a new run space is created, and a value of 0 indicates that a cache run space is used or not required;
Run space delay Time (ms)-time spent creating Windows PowerShell running space requirements;
Activation of the run space-the number of cmdlets running in Windows PowerShell where the running space is activated;
Run space activity time (milliseconds)-the total time of the Windows PowerShell runtime remains active when the space is requested. This includes activating the running space, invoking and executing the cmdlet, transforming the output object and the time required for errors in the process;
Windows PowerShell calls count-the number of times that Windows Poershell is called to run the cmdlet;
Call time in Windows PowerShell (milliseconds)-time spent running using the Windows PowerShell cmdlet. This includes the cmdlet once used in the Windows PowerShell engine itself;
Instantiated cmdlet-the number of cmdlets that the exchange was instantiated by the request. In some cases, this does not necessarily mean that a small command is actually invoked;
Cmdlet time (MS)-time spent in the code of the Exchange cmdlet. This includes time in the constructor, Beginprocessing,processrecord and endprocessing flowers;
The invocation of the cmdlet-the exchange number of cmdlets is invoked through a valid Windows PowerShell. This basically calculates how many times beginprocess is called in the Exchange cmdlet;
BeginProcessing Time (MS)-the time spent in the Exchange cmdlet runs beginprocessing;
Processrecord count-the number of times Processrecord is known as the Exchange cmdlet. The value indicates the number of inputs by the process of the object of the Exchange cmdlet during the request;
Process recording time (milliseconds)-the time spent in the Exchange cmdlet runs Processrecord. This usually includes most of the requested LDAP and RPC calls;
EndProcessing Time (MS)-the time spent in the Exchange cmdlet runs endprocessing.

This article from "Gs_hao" blog, declined reprint!

Exchange 2016 starts the Exchange EAC Performance console interface