Total Active Processes Supported

Hi Team,
I have a question related to the capacity management. We are designing a system where a workflow is started whenever a paper record is handed over to collection centers across multiple geographical locations. Once the work flow is created it gets assigned to different users before it moves to closure. Average days the work flow will remain open is 2-3 days. (i.e some of the users will take a day or 2 to complete their work). We are expecting around 100K paper every day ,which creates 100K processes every day. Considering the SLA of 2-3 days we will have around 300K processes simultaneously active in system. (some will be lying in the Task list of a user group ,some will be worked upon by users etc). Is this volume something supportable or do we need some special topology for accommodating this volume.

OriginalPostID-273629

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer
    It is supported, but keep your processes light.
    For example,
    - store things in cdts
    - don't store same value in multiple cdts
    - minimize chaining
    - reduce / consolidate smart services
    - move things to sub processes where no user activity and archive/delete after completion
    - set data management

    Also, run health check. Early and often.

    Hope those help.
Reply
  • 0
    Certified Lead Developer
    It is supported, but keep your processes light.
    For example,
    - store things in cdts
    - don't store same value in multiple cdts
    - minimize chaining
    - reduce / consolidate smart services
    - move things to sub processes where no user activity and archive/delete after completion
    - set data management

    Also, run health check. Early and often.

    Hope those help.
Children
No Data