Last week I worked with a client that runs a custom application on Microsoft CRM 4.0 and experienced performance problems in their test environment. Individual web requests to query or update data took several minutes, with some of them eventually timing out. We analyzed some of these long running and failing transactions and in this blog I present my analysis and hope it will be beneficial for other MS CRM Developers.
Problems we have found
We focused on specific individual transactions that either ran slow or timed out. We identified the following 3 Top Performance Problems:
- Problem 1: Too many Database calls through CRM Web Service SDK
- Problem 2: CRM Service calls always use Web Service Stack
- Problem 3: Database Contention