topic Re: Production performance tuning in Alfresco Archive

Production performance tuning

bwd — Wed, 27 Apr 2011 15:59:41 GMT

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 threa

Re: Production performance tuning

ronald_van_kuij — Wed, 27 Apr 2011 19:08:11 GMT

Your analysis is good.

The jobexecutor might need tuning to but check if it is a bottleneck first since afaik configuring it not exposed (yet?) in the config (see) modules/activiti-engine/src/main/java/org/activiti/engine/impl/cfg/ProcessEngineConfigurationImpl.java but harcoded in modules/activiti-engine/src/main/java/org/activiti/engine/impl/jobexecutor/JobExecutor.java

The engine itself has a low fairly low footprint, so I'd not care about that. Each process instances that is in a waitstate (usertask, receivetask etc) does not occupy any memory. A process instance only occupies memory if it is actually loaded from the db because it has to 'run'. How much is dependend on e.g. variables loaded etc, but it is not high either.

Adding indexes should indeed be done according to your needs since the default engine cannot cater for all usecases. A query analyzer helps a lot here.
Adding to many howeve can lead to performance degradation since the index has to be updated each time a record is added but I suspect you already know that.

Re: Production performance tuning

jkronegg — Fri, 25 Jul 2014 07:52:07 GMT

From my experiments:

Each ProcessEngine has a memory footprint of about 4 MB.
The deployed processes do not use memory since they are stored in the database. However, they are cached into ProcessEngineConfigurationImpl.getProcessDefinitionCache() which is basically a HashMap so if you deploy thousands of processes, your memory footprint will rise. If you deploy a lot of processes, you should use a smarter process definition cache, e.g. one based on soft references so that the cache is garbage collected when the memory is low.