locked
Production issue - CRM behind F5 RRS feed

  • Question

  • We are running CRM 2011 in an enterprise on-premise environment. Our customizations are primarily in javascript and plugins.

    We ran load tests at a remote site against our application and saw good results in the QA environment.

    Now we are migrating to a production environment with an F5 for load balancing. Our application load times are unacceptably long at remote locations. The issue is sporadic.

    Does anyone have any insight or tips into operating CRM behind an F5. Anyone experience this type of issue?

    Ever Grateful,

    Kevin

    Wednesday, April 11, 2012 11:34 PM

Answers

  • Hi Kevin,

    It is very hard to judge your scenario. Sporadic long load times could also be related to a process in CRM which could kind of choke the network.

    One such scenario way back in one of my CRM projects was the use of Dynamics Work sheets. I had 3 servers load balanced in London and users in Asia got a slow response intermittently. One of the reasons we found was excel dynamics worksheets. Whenever users used those and huge data was supposed to update the excel, the CRM went slow.

    It could be issues with your SQL Server running into high memory. In terms of SQL you can run SQL profiler at the time when you find your CRM running slow. This way you can find the culprit TSQL if any.

    Check your windows, IIS and CRM logs around the time when CRM is slow. Enable CRM tracing around the time when CRM is slow.

    It can also be due to many processes (workflows) failing or in waiting position (generally means some error, unless you have wait or timeout conditions). If CRM is slow, check your system jobs.

    So from hardware point of view I cannot comment, but from software point of view most likely the cause could be CRM/SQL Server.

    I hope this helps. If my response answered your question, please mark the response as an answer and also vote as helpful.


    Ashish Mahajan, CRM Developer, CSG (Melbourne)
    My Personal Website: http://www.ashishmahajan.com
    My Blogs: http://ashishmahajancrm.blogspot.com.au and http://ashishmahajancrm.wordpress.com
    My Youtube Channel: http://www.youtube.com/user/ashishmahajanmscrm

    My Linkedin: View Ashish Mahajan's profile on LinkedIn
    My Twitter: https://twitter.com/#!/ashishmahajan74

    Wednesday, April 11, 2012 11:50 PM

All replies

  • Hi Kevin,

    It is very hard to judge your scenario. Sporadic long load times could also be related to a process in CRM which could kind of choke the network.

    One such scenario way back in one of my CRM projects was the use of Dynamics Work sheets. I had 3 servers load balanced in London and users in Asia got a slow response intermittently. One of the reasons we found was excel dynamics worksheets. Whenever users used those and huge data was supposed to update the excel, the CRM went slow.

    It could be issues with your SQL Server running into high memory. In terms of SQL you can run SQL profiler at the time when you find your CRM running slow. This way you can find the culprit TSQL if any.

    Check your windows, IIS and CRM logs around the time when CRM is slow. Enable CRM tracing around the time when CRM is slow.

    It can also be due to many processes (workflows) failing or in waiting position (generally means some error, unless you have wait or timeout conditions). If CRM is slow, check your system jobs.

    So from hardware point of view I cannot comment, but from software point of view most likely the cause could be CRM/SQL Server.

    I hope this helps. If my response answered your question, please mark the response as an answer and also vote as helpful.


    Ashish Mahajan, CRM Developer, CSG (Melbourne)
    My Personal Website: http://www.ashishmahajan.com
    My Blogs: http://ashishmahajancrm.blogspot.com.au and http://ashishmahajancrm.wordpress.com
    My Youtube Channel: http://www.youtube.com/user/ashishmahajanmscrm

    My Linkedin: View Ashish Mahajan's profile on LinkedIn
    My Twitter: https://twitter.com/#!/ashishmahajan74

    Wednesday, April 11, 2012 11:50 PM
  • Hi, in addittion to Ashish's post, a good tool for finding where the long load times are coming from is fiddler:

    http://www.fiddler2.com/fiddler2/

    If you capture a trace and look at time line you can establish where the wait time is coming from.

    Hth,

    Scott

    

    Scott Durow
    Read my blog: www.develop1.net/public
    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Thursday, April 12, 2012 6:02 AM
    Answerer
  • Hi Kevin,

    If any of the responses answered your question and you are satisfied, please mark the response as an answer and vote as helpful. This will help others to search on similar problems.

    Thanks in advance.

    Ashish Mahajan, CRM Developer, CSG (Melbourne)
    My Personal Website: http://www.ashishmahajan.com
    My Blogs: http://ashishmahajancrm.blogspot.com.au and http://ashishmahajancrm.wordpress.com
    My Youtube Channel: http://www.youtube.com/user/ashishmahajanmscrm

    My Linkedin: View Ashish Mahajan's profile on LinkedIn
    My Twitter: https://twitter.com/#!/ashishmahajan74

    Friday, April 13, 2012 3:37 AM