You’re offline. This is a read only version of the page.
135
Hi there,
We are using v8.1 in the cloud, soon to upgrade to v9 and our users (350 approx) are complaining, have pretty much from the start, about performance. In particular, the time taken for the global search to return a contact is causing the most pain where a user can be waiting up to 10/15 seconds for a contact to be found. We notice that if you filter it by contact, it's quicker or if you click on the search icon twice. Also, simple items such as getting a quick create form to render can sit there for 2 to 3 seconds before it will display. The performance can vary depending on the time of the day etc. which adds inconsistency to the UX and a general undercurrent of frustration that is hurting adoption. We have tried to tune the global search - which includes some custom entities, monitored data performance logs for optimization, asked Microsoft to carry out analysis and tune the back end db and while there was some improvement using all these measures, it hasn't been enough.
As a public body we have large internet bandwidth available to us and the problem can persist around our site over different switches etc. so I figure it can't be a network or a workstation issue.
All users are instructed to use chrome that has, in most cases, been configured to clear the cache for the dynamics website on exist. We found the cache wasn't expiring naturally so screens wouldn't render properly, new subjects wouldn't appear and other oddities that were fixed by this. Users are ok with the first load being a little slower by the actual fact that they don't even notice it compared to general performance.
We don't have the forms heavily customized and anyway, even the quick forms can take a while to render as well.
So at this stage, I am now starting to wonder, whether we should start to consider drastic measures such as moving to on premise? I have noticed that a lot of organisations using dynamics seem to be on premise, one has even told me this is for performance reasons. The others I always assumed was because they just started out before SAAS was a viable option. We started as SAAS, should we consider moving on premise, would it improve performance significantly? Having the infrastructure maintenance and application administration would be an unwanted headache. What are the other main disadvantages of moving back on premise?
Thanks in advance.
J
*This post is locked for comments
I have the same question (0)
If you can manage the on-premise servers, ops team, upgrades, patching, maintenance headaches then moving to onpemise is fine.
On the other hand, high availability (99.99%) on cloud, MS Azure infrastructure are big trade-offs.
You can negotiate with MS for moving your Org to different scale group or even a dedicated scale group with use cases/business impact.
Share
Report
All responses (
Answers (
