Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
MS CRM 2013 - Can we accomodate more number of Concurrent Users, when we use two different Servers for Frontend and Backend Servers for Asynchronous Services. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    MS CRM 2013 - Can we accomodate more number of Concurrent Users, when we use two different Servers for Frontend and Backend Servers for Asynchronous Services?
    Wednesday, May 6, 2015 7:22 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    In general terms, yes.

    To be more specific, you should investigate where the load is generated, if you have heavily loaded front end servers you would need extra front end servers set up with load balancing. If you have a lot of workflows running you need more power on the asynch side. I can't say if it's better to have more servers or to beef up the existing servers.

    Hope it helps.

    Rickard Norström Developer CRM-Konsulterna
    http://www.crmkonsulterna.se
    Swedish Dynamics CRM Forum: http://www.crmforum.se
    My Blog: http://rickardnorstrom.blogspot.se

    Wednesday, May 6, 2015 8:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Rickard,

    In the current setup we are having both the roles(CRMFrontend and CRMBackEnd) in the same windows Server and it is supporting 300 Simultaneous Users as the load on Both CRM FrontEnd and BackEnd are almost equal.

    Is it possible to increase number of Simultaneous Users in case CRMFrontend and CRMBackEnd Roles are separated and assigned to different servers? If yes what is the Microsoft recommendation of increase in Concurrent Users in this scenario.

    Thanks,

    Rajeev.

    Wednesday, May 6, 2015 10:54 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The load balancer will use an algorithm to split the users connections to the front end servers.  You don't assign users to a specific front end server.  The users could potentially be given the url for a specific machine name if they were using the web client to connect but you would likely see issues.  Especially with custom code.  And it also defeats the purpose of load balancers.

    The same with the back end server.  The load balancer will assign connections for an async service to connect and grab jobs from whatever backend server has the least workload based on the built in logic of the load balancer.  The async service grabs a specific number of jobs to process each time.  So if the first server grabs the first group, and there are not that many left, theoretically the second back end server could have a lighter workload. 

    So you need to monitor the workload to determine how many of each front end and back end need to be added.  Each environment is unique and defendant on hardware.

    Jason Peterson

    Thursday, May 7, 2015 11:25 PM