# Version6.8.1，about performance of task.complete

**URL:** <https://forum.flowable.org/t/version6-8-1-about-performance-of-task-complete/12553>\
**Category:** Flowable Engine\
**Created:** [March 13, 2026, 5:56am UTC](https://forum.flowable.org/t/version6-8-1-about-performance-of-task-complete/12553 "2026-03-13T05:56:06Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [March 13, 2026, 8:07am UTC](https://forum.flowable.org/t/version6-8-1-about-performance-of-task-complete/12553/2 "2026-03-13T08:07:49Z")

</div>

the core and max pool size should be set to the same value - the JVM has a weird setting that it only starts to add more threads once the queue is full (which is 1000 for you).

However, if you’re using Spring Boot, make sure to use the right properties: have a look at this recent forum post: [Flowable 7.2.0: Node Affinity Hoards All Jobs – All Async Jobs Locked by Node 1 while only 8 are being processed - #10 by ROY](https://forum.flowable.org/t/flowable-7-2-0-node-affinity-hoards-all-jobs-all-async-jobs-locked-by-node-1-while-only-8-are-being-processed/12547/10)

---

_[View the full topic](https://forum.flowable.org/t/version6-8-1-about-performance-of-task-complete/12553)._