In this post I'll be discussing the second part of troubleshooting and tuning performance with CRM Online. In my last blog post, Microsoft CRM Online Performance Tips & Tricks - Part 1, I explained where to start with troubleshooting performance with CRM Online; evaluating user expectations and the different areas of the application, measuring performance, and establishing a baseline. Once we have that information, we then started to look into the various parts that can affect performance, which we looked at hardware and software. Continuing on with the other parts that affect performance, below I'll discuss: network connectivity, customizations, and the CRM client for Outlook.
Connectivity to the CRM Online service is probably one of the larger areas that people think is a contributor to performance. In many cases the end users network connection to the CRM Online service is adequate. What do we deem as an adequate connection to the service?
The way to measure this speed is with the CRM Online Diagnostics Page. Substitute your Organization Name in the URL below.
If your connection is not within the adequate range for all users, some users, or some locations, start to narrow down what is different.
A CRM Online deployment's customizations are often the biggest area that can affect performance that customers don't realize.
The last component to consider is the CRM Client for Outlook. There are a number of configuration settings that can impact the performance of machine running the CRM Client for Outlook, namely sync process, email tagging and some functionality.
In these two posts on performance with CRM Online there are a large number of considerations and all of them are important and can affect customers at varying degrees. As you make each change measure your performance so you know what changes are improving your performance and by how much. In making multiple adjustments that give you small gains which in the end will add up to a noticeable improvement in performance for end users.
Microsoft Premier Field Engineer
Great article :)