This blog will give you all possible information about Performance Optimization for Dynamics CRM 2011.
Performance Optimization for Dynamics CRM 2011
- Client side
- Server Side Configurations
- Database level
Deciding factors to improve the performance of CRM client.
It depends “How quickly you get the response from the browser and once you receive it how fast you render the objects from the response on the page”.
Measure in the system to confirm that we need to improve the performance.
- Time to First Byte
- The time the browser receives the first byte from the server after a request has been made. It is all about optimizing the traffic, if we can optimize the traffic, we can reduced the traffic and eventually the performance improvement will happen.
- Render Start Time
- The start render time is the moment something first displays on the user’s screen. Optimizing start render time is mainly a function of server response and optimizing the efficiency of the elements in the HEAD of HTML documents.
- DOM Content Loaded
- The DOMContentLoaded event is triggered when the page’s Document Object Model (DOM) is ready, and when the document has been completely loaded and parsed, without waiting for style sheets, images, and sub frames to finish loading.
- Page Load Time
- Time to load the entire page.
After going through all these scenarios and with my experience I feel the best solution for this client side performance is the “Simple & efficient customizations”
The Java script also can reduce the performance. So it is better to load the required script when you really required.
And the other factor is the Ribbon customizations. Contextual ribbons.
Here is a checklist which can help us identifying and reduce the issues with our client performance:
- Optimize Form Load Experience.
- Keep less fields on the form.
- Do not over use scripts (Avoid OnLoad; Use OnChange since its on demand).
- Trim the ribbon appropriately.
- Be wary of client side enabled rules.
- Use collapsed sections whenever possible.
- Use server side show/hide fields.
- Use ‘read optimized’ forms.
- Use iFrames carefully, the more you have longer it takes to load.
- Use Sub-grids, where necessary as it tend to increase page size quickly.
- Manage the complexity and visualizations of dashboards.
Server Side Configurations: (High Level)
- Using Compression Techniques
- Compression techniques designed to optimize network performance directly affect the size of the data files transmitted over the network
- Configuring HTTP Compression
- Using WAN Accelerator Hardware
- Configuring Proxy Server Settings
- Reducing E-Mail Traffic by Modifying Outlook Rules
- Data cleanup on PrincipalObjectAccess table
- Data cleanup on AsyncOperationBase table.
- For every async operation happens in Dynamics CRM 2011, a record gets saved in Asyncoperationbase table. So there is a possibility to grow this table very fast. To control growing this table size and save disk space, need to set “Automaticlaly delete completed workflow jobs” & “Delete AsyncOperation If statusCode =Successful” settings are done in Workflows and Plugins.
Hope this helps!