Monitoring Mobility Service Usage
Topic Last Modified: 2011-11-22
On an ongoing basis, you should monitor the CPU and memory that is used by the Microsoft Lync Server 2010 Mobility Service. To monitor usage, you can use either of the following:
The CSIntMcxAppPool and CSExtMcxAppPool worker processes in Internet Information Services (IIS) Manager. In the Worker Processes pane, look at the CPU % and Private Bytes (KB) (memory) columns.
The CPU and Processor performance counters.
For most deployments, Mobility Service CPU usage should be below 15% on average. Memory usage should fall within the limits described in Monitoring for Server Memory Capacity Limits.
In addition to CPU and memory usage counters, you can use the following ASP.NET performance counters to help determine when a server is overloaded with requests:
- ASP.NET v2.0.50727\Requests Current, which indicates the number of pending web requests on the server. When this counter reaches 5,000, subsequent requests will fail with error "503 - Service Unavailable".
- ASP.NET\Requests Queued (should always be zero)