NEIL PARKHURST

USD – Faster load times using the cache

October 31, 2015

When the USD application loads various user and configuration settings need to be loaded from the server, this can take time. The load time of USD can be reduced by forcing a local cached of these settings.

The advantage being that the USD application will load faster, the disadvantage being that you’d need to remember to update your USD options to force a refresh of the local data following each change.

NOTE: A word of caution, the cache contains USD settings but seems to also hold information from other entities such as the CRM system user. Any changes to a configuration option that directly or indirectly effects the USD operation could mean a refresh is needed.

The process of enabling the cache is a simple one, go to the USD settings and select options.

Now add a new user option called “ClientCacheVersionNumber”

The value parameter is used to hold the current version number of your USD application. When a new version is available, increase this value to reflect the change. When USD loads the change in this value will be detected and the USD cached data will be refreshed.

13 responses to “USD – Faster load times using the cache”

Learning USD | My experiences with Microsoft Dynamics CRM

October 14, 2015 at 6:01 am

[…] Load speed( cache) […]

LikeLike

Reply
Learning Unified Service Desk – Microsoft Dynamics CRM Community

October 31, 2015 at 10:33 am

[…] Load speed( cache) […]

LikeLike

Reply
Learning Unified Service Desk | Microsoft Dynamics CRM and Unified Service Desk

January 3, 2016 at 6:02 pm

[…] Load speed( cache) […]

LikeLike

Reply
USD – The Book | Microsoft Dynamics CRM and Unified Service Desk

June 20, 2016 at 6:03 pm

[…] Faster load times […]

LikeLike

Reply
popeye

September 14, 2016 at 3:31 pm

Hi Sir, Can you please describe about the USD performance related issue. Like on CRM my “New” Case form opens at 12 second but on USD it is taking around 20 seconds. How can I reduce it ? AHT is really high due to this….Any comment !

LikeLike

Reply
1. Neil Parkhurst
  
  September 14, 2016 at 4:05 pm
  
  Interesting, in my experience I haven’t noticed a significant difference when opening CRM pages inside USD and outside. When your case form loads do you have any additional actions doing anything extra. Such as loading the related account at the same time? In a previous project we did di some performance issues due to increased memory usage of having USD. But that was in a thin client environment so quite a specific issue.
  
  Even 12 seconds sounds quite long to load a new case. Is it CRM online or on premise?
  
  LikeLike
  
  Reply
popeye

September 14, 2016 at 4:34 pm

Thanks for quick revert. 1.) Nothing Loading at the same time as you mentioned related account. 2.) This implementation is on CRM 2015 on-premise. 3.) At onload of “Case” entity CRM form we have JS

We disable the same JS then we find some positive difference then the “New” case form is opening at 10 seconds & USD “New” case form is opening at 15 seconds

On an avg. USD is taking 6 more seconds to open New case form then the same at CRM on web.

USD Version we are using 1.2, should we upgrade to latest USD version (But i am bit worried that whether it will impact on USD configuration or we should only install the USD Client application.)

I am talking here about NEW Case form specifically as in our scenario, when a customer call lands then a “New case” form open & the number tagged on one field which is “called no.” & if the no. matches using JS (O-data query), at customer field, customer will populate.

You mentioned here at Cache…will this can help here…Any comment ?

LikeLike

Reply
1. Neil Parkhurst
  
  September 14, 2016 at 5:10 pm
  
  You should use the cache option I describe on production. BUT that will only improve the load time of USD. It won’t help with the load of your case form.
  
  I personally would go for the latest version of USD solutions and clients. As certainly some of the improvements have been performance related.
  
  BUT I have no experience of deploying those on a CRM 2015 organisation. I have only used the latest CRM 2016 Update 1. You should therefore test them carefully before applying to your production environment.
  
  In terms of compatibility between versions I have not experienced any difficulties. The definition of the USD entities has largely remained the same between versions. Although at the latest upgrade I think some changes might have been made. Hence why testing is key.
  
  I think you could safely trial the latest client without updating your solutions. Especially as that would be easy to revert back it happened to cause an issue. I think I would try that first.
  
  USD will consume slightly more memory than CRM alone. You should double check the memory usage on the clients. But if you are running on clients with 8Gb then you should be fine. (And that would be a pretty typical entry level these days.)
  
  LikeLike
  
  Reply
2. Neil Parkhurst
  
  September 14, 2016 at 5:17 pm
  
  Also … an obvious one. All your hosted controls are IE Process aren’t they??
  
  LikeLike
  
  Reply
popeye

September 15, 2016 at 10:28 am

Hi Sir, The “case form” hosted control is internal WPF here but i changed it to IE Process but didn’t find improvement. I chose here internal WPF to avoid “event” popups.

When I upgraded USD to latest version, we find some improvement

can you please suggest any other measures…. ?

LikeLike

Reply
1. Neil Parkhurst
  
  September 15, 2016 at 11:31 am
  
  Have you seen this post to avoid the event popups?
  https://blogs.msdn.microsoft.com/usd/2016/01/26/ie-process-mode-gives-httpevent-popup/
  
  I understand that when loading just one tab you might not see much difference between IE Process and WPF Internal. But IE process will handle memory better and when loading multiple tabs concurrently IE process should be faster. It is the recommended approach.
  
  LikeLike
  
  Reply
popeye

September 15, 2016 at 5:57 pm

Hello sir, Someone suggested me to hide navigation bar (at case entity form) in USD to improve form opening performance. But the navigation rule which is made for this purpose is unable to hide navigation bar when i chose the related option there, also at the action call I put “Hidenav=true” but this didn’t trigger.

You mentioned about the same here
https://neilparkhurst.com/2015/11/12/usd-load-account-and-primary-contact/comment-page-1/#comment-2046 .

Didn’t you find any solution ?

Thanks !

LikeLike

Reply
1. Neil Parkhurst
  
  September 15, 2016 at 6:15 pm
  
  I am not sure hiding the nav bar will make a difference. But I guess anything is worth a try.
  
  I have never managed to get the Hidenav=true to work! I have experimented with a few options.
  
  I have only been able to hide the navigation using the window navigation rules.
  
  LikeLike
  
  Reply