locked
Best practices to decrease the load on Asynchronous Service (Any design/architecture level changes/any advices etc.) RRS feed

  • Question

  • Hi All,

    Any Best practices to decrease the load on Asynchronous  Service (Any design/architecture level changes/any advices etc.) 

    Thanks in Advance,

    Shaik

    Tuesday, July 2, 2013 7:03 AM

All replies

  • The load on the asynchronous service is due to the number of system jobs. The main ones that you could remove are:

    • Workflows
    • Asynchronous plugins
    • Scheduled jobs, like duplicate detection jobs
    • Data imports

    However, if you require the functionality of these, there aren't many alternatives. In many (but not all) cases asynchronous plugins could be configured to run synchronously, but this just moves the load to the IIS worker process.

    Overall, there's not a lot you can do to reduce the load on the Asynchronous Service, so the alternative is to increase the capacity, for instance by adding more servers with this role


    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Tuesday, July 2, 2013 8:04 AM
    Moderator
  • Hi,

    It's also worth asking why you want to decrease the load? - is it because it is on the same server as the front end role - in which case you could create a dedicated server with the back end role on it. You can have multiple back end servers and they each will pick off jobs from the asyncoperation table.

    hth


    Scott Durow
    Blog www.develop1.net    Follow Me
    Rockstar365
    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Tuesday, July 2, 2013 8:10 AM
    Answerer