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 ?

Parents
  • As the others have mentioned, it is not truly the number, but instead their footprint. Keep your processes light and archive as soon as possible. Keep your processes light by reducing nodes, chaining, PVs, etc.

Reply
  • As the others have mentioned, it is not truly the number, but instead their footprint. Keep your processes light and archive as soon as possible. Keep your processes light by reducing nodes, chaining, PVs, etc.

Children
No Data

 Discussion posts and replies are publicly visible