Scalability and performance tuning aspects

[fleroux]

Hi folks,
I am currently evaluating activity for my company ; product looks great and feature rich. Thanks! A key aspect that I would like to understand better is the scalability and performance capabilities. I've noted http://www.mulesoft.org/activiti-bpm which states "Activiti runs in any Java application, on a server, on a cluster or in the cloud."

Questions:
- how do I configure activity in a cluster (active/active and sticky state/session failover or loadbalancing required)
- how do i scale the process engine (assuming this is the area where concurrent contention might occur)? vertical scaling possible? similarly , the workflow scaling (i.e. threading) capabilities would be useful to understand (i.e. so that i can understand the vertical & horizontal options available)
- if i wanted to test a scenario where I get frequent events that would trigger a workflow and therefore i need to be able to throttle and/or tune the workflow throughput (i.e can i multi thread and also throttle a workflow; sort of like Q based multi messaging and Q depth thresholds)
- I noted the reference to mule as an integrated option that provide some of the scalability aspects? if so pls advise where I can find how this is configured ? I'd like to understand which aspects the mule deployment model addresses and how (both processengine and workflow scalability)

Where can I find documentation that will enable me to configure and test these questions/answers please? (or if yo have the answers then please shoot!)

your help is appreciated and great product!

thanks
frank

[heymjo]

a few thoughts on scalability

- Look at exclusive jobs and the way they are executed http://forums.activiti.org/en/viewtopic.php?f=6&t=3614

- You would want to configure org.activiti.engine.impl.persistence.StrongUuidGenerator on the processengine configuration instead of keeping the default dbid generator

- Configured audit level plays a role in performance, though i have not got exact numbers

- Presumably your process definition itself plays a part in scalability, some process definition by their structure and flow might scale well and others might not. Empirical research is in order here