web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Workflows and Performance

(0) ShareShare
ReportReport
Posted on by 70

Hello,

We have an app server and a DB server for MSCRM 2011 on premise. The Asynch Service is hosted on the App Server. We have an average of around 50,000 workflows that run each business day. I'm looking for feedback on the depth of this. Can we improve performance by reducing the number of these workflows that run each day? Lately, we have been seeing sporadic slow load times when navigating the front end of CRM 2011 and I'm trying to isolate the root cause.

50,000 seems like a lot daily, I don't have anything to compare or gauge it against though.

I did some reading and it seems like you can have multiple asynchronous services on different servers to help load balance workflow and other plug-in SDK tasks that run.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Wayne Walton Profile Picture
    13,730 on at

    50,000 is A LOT daily.  Your AsyncOperationBase table is likely gigantic, and slowing things down to a crawl (unless you're already cleaning this, then good job) Link for info: support.microsoft.com/.../en-us

    But yes, you can install the Async service on multiple back-end servers to relieve load, if you don't see a practical way of reducing the daily workflow count.  You can find some good information in the CRM Deployment Guide, but the core concept isn't difficult.  

    Also, for good deployment design, I'd split up your App server into front-end and back-end roles.  This does a couple important things:

    1. If you really are killing performance with your workflow load, splitting the back-end server work will dramatically improve user experience, even if the async service itself is backlogged.

    2. It becomes easier to scale out your deployment of your back-end servers in a balanced way, as you don't have to take into account different workloads for different servers.

  • mkweick Profile Picture
    70 on at

    Detailed response, Great Info!

    When you say split up the App Server into front end and back end roles, are referring to moving all the asynch services off the app server over to back end servers and just leaving the CRM Application on the front end app server?

  • Wayne Walton Profile Picture
    13,730 on at

    You're welcome.  :)

    As for your question, here's a clarification.  During the install process, there are three key roles, the front-end, back-end, and SQL server roles.  Front-end is the web server, the stuff a user will see.  Back-end is Async (and commonly deployment) processes, and then the last server is the SQL server itself.  Ideally, these all get installed on their own server.

    That gets you maximum performance isolation, so your async service can't choke off your front-end server's resources.  

  • mkweick Profile Picture
    70 on at

    Wayne,

    I can't thank you enough for this info. You have my vote!

    Thanks and take care.

  • Wayne Walton Profile Picture
    13,730 on at

    You're quite welcome.  

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans