How many scheduled processes are considered "too many" ?

Let's assume that our Appian instance is going to manage several processes which are basically poller, doing these tasks:

  1. retrieve data from rest urls or datasources (the payload could vary between 1kb to 5mb)

  2. apply some kind of basic data manipulation on the retrieved data
  3. save the manipulated data in a database

Let's say that we have:

  1. 20 processes running 24/7 every 30 seconds
  2. 10 processes running 24/7 every 2 minutes
  3. 15 processes running 24/7 every 1 hour
  4. 10 processes running 24/7 every 6 hour

In conclusion, we have something like 55 processes, let's round them to 60, which are doing the tasks listed above. Is this setup critical in terms of performance and system reliability ?

  Discussion posts and replies are publicly visible

Parents
  • Certified Lead Developer

    It's not the number of processes that's going to be the problem, but the overall aggregate effect they're going to have on your system.  Fine tuning them will probably net you more performance boost than reducing the frequency with which they run.

    Check out how your database resources respond, what happens to your CPU and RAM.  The size each one gets to and the length of time they sit before being archived are going to be some big factors to look into.

Reply
  • Certified Lead Developer

    It's not the number of processes that's going to be the problem, but the overall aggregate effect they're going to have on your system.  Fine tuning them will probably net you more performance boost than reducing the frequency with which they run.

    Check out how your database resources respond, what happens to your CPU and RAM.  The size each one gets to and the length of time they sit before being archived are going to be some big factors to look into.

Children
No Data