Applies to Dynamics 365 (online), version 9.x
Applies to Dynamics 365 (online), version 8.x
The primary characteristics of a network that affect the performance of Dynamics 365 clients, such as the web application or Dynamics 365 for Outlook, are bandwidth and latency.
Bandwidth is the width or capacity of a specific communications channel.
Latency is the time required for a signal to travel from one point on a network to another, and is a fixed cost between two points.
One of the main causes of poor performance of Dynamics 365 clients is the latency of the network over which the clients connect to the Dynamics 365 organization. Lower latencies (measured in milliseconds) generally provide better levels of performance.
Notice that, even if the latency of a network connection is low, bandwidth can become a performance degradation factor if there are many resources sharing the network connection, for example, to download large files or send and receive email.
Networks with high bandwidth don’t guarantee low latency. For example, a network path traversing a satellite link often has high latency, even though throughput is very high. It’s common for a network round trip traversing a satellite link to have five or more seconds of latency. An application designed to send a request, wait for a reply, send another request, wait for another reply, and so on, will wait at least five seconds for each packet exchange, regardless of the speed of the server.
How to check latency
Dynamics 365 includes a basic diagnostic tool that analyzes the client-to-organization connectivity and produces a report. To run the Dynamics 365 Diagnostics tool, follow these steps.
On the user’s computer or device, start a web browser, and sign in to a Dynamics 365 organization.
Enter the following URL, https://myorg.crm.dynamics.com/tools/diagnostics/diag.aspx, where myorg.crm.dynamics.com is the URL of your Dynamics 365 (online) organization.
The report displays a table with test and benchmark information. Of particular importance is the Latency Test row value. This value is an average of twenty individual test runs. Generally, the lower the number, the better the performance of the client. Although users may receive a satisfactory experience by using connections with more latency, for best application performance we recommend that the value be 150 ms (milliseconds) or less.