I am planning to use flowable in production. I am in search of benchmark numbers for flowable on AWS environment or any other environment.
My key observations will be on below:
How many parallel task it can execute? Both synchronous and asynchronous tasks.
How many parallel process instance it can support?
Since I have big tenants with 50K processes currently defined, I need the numbers for capacity planning of infrastructure.
Sounds cool.
This is not an easy question to answer, because it’s very important what kind of logic is executed in your process definitions. Are there a lot of REST calls, or is it more a chaining of user tasks? How many users will execute task queries concurrently? How many process instance or execution level queries do you expect in your application. So there’s more info needed to be able to answer your question.
Well the first post is for v6 and the asynch history is still disabled by default (as far as I know) and only mentioned as an experimental feature in the 6.2.0 documentation.
Yes async history is disabled by default, because it mainly makes sense if you use another db for the history information, like ElasticSearch. When we have more feedback from the community we will remove the experimental feature marker in 6.3.0.
But it does give a good reminder to do another benchmark test blog about the current state of Flowable.