The verdict is that jBPM is a very efficient workflow engine, it only requires turning the right knobs in order to get the most out of it.
That is indeed the spot that we're working hard to resolve in jBPM 4: better tuning defaults and that way try to postpone the need for custom tuning when scaling out.
By adding 3 servers and tweaking jBPM configuration, we were able to increase the throughput over 16 times in comparison to 1 server environment with default setup.
Awsome !
Tom, why don't you link the original article so your readers can jump to it quickly?
ReplyDeleteThanks, Alejandro. I must have been sleeping while posting this. The link is added now.
ReplyDeleteTom,
ReplyDeleteWhen is the next release of jBPM v4 due out? We have a number of interesting requirements I would be interested in running past you.
Regards
Shaun
Shaun,
ReplyDeletejBPM 4 will go GA on July 1st. http://www.jboss.org/community/docs/DOC-13217
New requirements can be discussed on dev forum: http://www.jboss.org/index.html?module=bb&op=viewforum&f=219
regards, tom.
I'm not cut out to be a programmer nor anything but I just I didn't know that turning the right knobs was the only way to resolve the problem with the jBPM.
ReplyDeleteHi there,
ReplyDeleteReally nice job,There are many people searching about that now they will find enough sources by your tips.
Also looking forward for more tips about that