When troubleshooting CRM performance issues everyone
typically wants to point fingers at the servers – whether it be SQL, CRM, or
even SSRS – but a commonly overlooked factor is the network. Not known to
everyone is a tool built into CRM called the CRM Diagnostics Page. It is
basically a very simple way to check network performance. To access the CRM
Diagnostics Page simply go to:
http(s)://<YourCRMServerURL>/tools/diagnostics/diag.aspx
This will land you at a page that looks like the following:
On this page, you can clearly see the series of tests
available but what are they?
1. Latency Test
This calculates the average time taken to download a small
text file 20 times. The file downloaded from the CRM server is
/_static/Tools/Diagnostics/smallfile.txt. CRM is designed to work best with
latency under 150 milliseconds. Latency can be a huge factor in performance for
offices far away the CRM server’s location.
2. Bandwidth Test
The bandwidth test downloads image files and records the
speeds. The recorded speeds are averaged together and provided in the results
summary. Bandwidth should ideally be higher than 50 KB/sec. This test, along
with the Latency Test, are the most helpful on this page.
3. Browser Info
This is a JavaScript pull of the local browser details such
as browser name, version, cookie status, operating system and the user-agent
string.
4. IP Address
This is the IP address of the client computer as known to
the server. The IP address is server-side dynamic and represents the IP address
which was used to contact the server.
5. JavaScript tests
The series of JavaScript tests times loops and returns their
execution time. They are essentially just memory/CPU stress tests on the client
machine.
6. Organization Info
Provides general server information- organization name, time
on server and client and URL.
Bonus!
This is also a neat little secret: http(s)://<YourCRMServerURL>/home/home_debug.aspx.
It has some of the same information as the diagnostics page - Not overly helpful but can possibly come in handy troubleshooting. I find it just to be a nice, concise page for deployment information to help with documentation.
No comments:
Post a Comment