We're planning production resources and are wondering if there are any sizing/tuning guidelines specifically for Activiti.
I'm guessing that the guidelines for things like database connection and thread pool sizes for the app server it's running in are pretty standard (basically, at least one thread and connection per required concurrent execution), but what about tuning settings for things like the internal job execution thread for timers, ..., etc?
Any estimates on the memory footprint for a process engine and process instances? Is memory usage growth tied to any run time activity that we can use to estimate memory requirements.
I do see some indexes on the database tables, which I assume cover the most frequent/expensive queries. Our usage is performing queries for processes and tasks based on variables set on the workflow processes. Should we be adding indexes to make these queries efficient as the data set size grows (if that's not already covered)?
Thanks in advance for any guidance.