cancel
Showing results for 
Search instead for 
Did you mean: 

Bad performance due to sleep() in AcquireJobsCmd

keymaster
Champ in-the-making
Champ in-the-making
The sleep(100) in

https://github.com/Activiti/Activiti/blob/master/modules/activiti-engine/src/main/java/org/activiti/...

caused a significant performance reduction.

Should I create an issue?
3 REPLIES 3

jbarrez
Star Contributor
Star Contributor
Did you try the async executor? It does not have that sleep method and performs better (for various other reasons).

keymaster
Champ in-the-making
Champ in-the-making
This currently is no option for our project, sorry. The Application is tested and staged for production.

We removed that sleep. The question is, if you want to fix that for other projects. A sleep in that method smells like a bug or a race condition.

jbarrez
Star Contributor
Star Contributor
>  The question is, if you want to fix that for other projects

No, because that sleep was probably introduced for a reason and it'll break other things.
We've created the Async Executor, which has proved to be far superior when it comes to performance. The old job executor will be deprecated in the future.
Getting started

Tags


Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.