Hello,
We don't have transaction mechanisms. Or I would say : there will be a transaction mechanism for loops only. That's why it is so fast.
Also : the model and links are not read from the DB. Everything is in the generated Java code.
Of course such a behavior is useful when we have Service Tasks only, no human tasks.
So it's faster because we almost don't use the DB, everything is in the Java code. And we can configure threads the way we want.
As far as we are concerned, we consider using //J as the engine for such kind of processes. We have a prototype actually working : we generate //J diagrams from Activi diagrams.