# BenchMark for Flowable performance **URL:** \ **Category:** Flowable Engine\ **Created:** [December 5, 2017, 5:47am UTC](https://forum.flowable.org/t/benchmark-for-flowable-performance/1295 "2017-12-05T05:47:46Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![renukaradhya](https://avatars.discourse-cdn.com/v4/letter/r/97f17d/32.png) [@renukaradhya](https://forum.flowable.org/u/renukaradhya)\ **Post date:** [December 5, 2017, 5:47am UTC](https://forum.flowable.org/t/benchmark-for-flowable-performance/1295/1 "2017-12-05T05:47:46Z")
Hi Flowable Team, 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. Please share the numbers . Thanks in advance. Regards, Aradhya ---
**Author:** ![tijs](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@tijs](https://forum.flowable.org/u/tijs)\ **Post date:** [December 6, 2017, 4:00pm UTC](https://forum.flowable.org/t/benchmark-for-flowable-performance/1295/2 "2017-12-06T16:00:09Z")
Hi Aradhya, 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. Best regards, Tijs ---
**Author:** ![PascalSchumacher](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/pascalschumacher/32/336_2.png) [@PascalSchumacher](https://forum.flowable.org/u/PascalSchumacher)\ **Post date:** [December 6, 2017, 6:35pm UTC](https://forum.flowable.org/t/benchmark-for-flowable-performance/1295/3 "2017-12-06T18:35:52Z")
As flowable is a fork of activiti, have a look at these posts for some general information: [http://www.jorambarrez.be/blog/2016/07/20/message-queue-async-executor-benchmark/](http://www.jorambarrez.be/blog/2016/07/20/message-queue-async-executor-benchmark/) [http://www.jorambarrez.be/blog/2015/07/20/the-activiti-performance-showdown-2015/](http://www.jorambarrez.be/blog/2015/07/20/the-activiti-performance-showdown-2015/) ---
**Author:** ![PHH](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/phh/32/94_2.png) [@PHH](https://forum.flowable.org/u/PHH)\ **Post date:** [December 6, 2017, 6:43pm UTC](https://forum.flowable.org/t/benchmark-for-flowable-performance/1295/4 "2017-12-06T18:43:57Z")
These posts are very out of date and for v5. Running v6 with the async history, for example, can make a big difference. Cheers Paul. ---
**Author:** ![PascalSchumacher](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/pascalschumacher/32/336_2.png) [@PascalSchumacher](https://forum.flowable.org/u/PascalSchumacher)\ **Post date:** [December 6, 2017, 7:05pm UTC](https://forum.flowable.org/t/benchmark-for-flowable-performance/1295/5 "2017-12-06T19:05:05Z")
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. ---
**Author:** ![tijs](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@tijs](https://forum.flowable.org/u/tijs)\ **Post date:** [December 6, 2017, 7:56pm UTC](https://forum.flowable.org/t/benchmark-for-flowable-performance/1295/6 "2017-12-06T19:56:03Z")
Hi Pascal, 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. Best regards, Tijs ---
**Author:** ![filiphr](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/filiphr/32/315_2.png) [@filiphr](https://forum.flowable.org/u/filiphr)\ **Post date:** [November 14, 2018, 6:59am UTC](https://forum.flowable.org/t/benchmark-for-flowable-performance/1295/7 "2018-11-14T06:59:09Z")
I think it is worth adding the latest performance benchmarks for the 6.3.0 release. [https://blog.flowable.org/2018/03/05/flowable-6-3-0-performance-benchmark/](https://blog.flowable.org/2018/03/05/flowable-6-3-0-performance-benchmark/) [https://blog.flowable.org/2018/03/13/async-history-performance-benchmark/](https://blog.flowable.org/2018/03/13/async-history-performance-benchmark/)