Will high numbers of process instances work

[n.belford]

Does anybody have any experience or knowledge of jBPM use in situations where high numbers of process instances are active simultaneously.

We are looking at a scenario tracking B2B transactions in Energy Reticulation Markets where about 5000 new process instances per hour would be generated (at a busy time) across about 10 different process definitions. Some of these instances would be quite long running with about 100,000 concurrent process instances. The process definitions would not be that complex.

I would greatly appreciate any feedback about this and I am specially interested in comments
1. about the outright feasibility of this idea
2. about how to scope hardware requirements
3. reference production systems that are of this magnitude or bigger.

Any help much appreciated


Neil Belford

[kukeltje]

The info I have:

1: If you just look at the jBPM core, yes, this would be feasable, most delay will be in DB access
2: 2 general sized servers (dual 3GHz, 8GB) would suffice is my guess. (I perosonally have no real figures, but I've done a small test on a lesser system with good results)
3: hmm..... That should come from JBoss guys or fellow forum users

The number of concurrent processes is no problem (just storage). The thing is how often they are acted upon. Tuning the DB (indexes) is also an important thing. The DDL scripts are generic.

[kbarfield]

Neil,

I work for JBoss and can help you with this. Please contact me at kevin[dot][e-mail].

Thanks,

Kevin