Performances impact when migrating from 5.17 to 5.18

[melanie1]

Hi,

I ve created a post on stackoverflow :
http://stackoverflow.com/questions/33397728/activiti-5-18-migration-and-performances-impacts
asking about the performances impact when migrating from activiti 5.17 to activiti 5.18. We have some simple unit tests checking the processing time required to process simple workflows, and we observe a double time increased in the processing of those workflows when migrating to activiti 5.18. We were expecting performances improvements, as mentioned in the release note, that some developments have been made in the database insertion. Indeed we observe that less time is spend on this step, however, we now have additional times spends manly in Context related methods (getStack, getCommandContext, getProcessEngineConfiguration, performOperation). I could give you the jprofiler recording session if this helps. But my question is therefore, would you expect such double time increase? Is there is any properties/configurations that are available in activiti 5.18 to tune performances?

Thanks and Regards,

Mélanie

[jbarrez]

No, i would certainly not expect a doubling in time. Could you provide a test setup that demonstrates this problem?

[melanie1]

Hi Joram,

Thanks for your reply. I will try to provide you shortly with a setup that isolate this issue.

Best Regards,

Mélanie

[jbarrez]

Thanks. Looking forward to investigating what could be it.

[melanie1]

Hi Joram,

Please find attached a small project ( I added _.txt to trick your upload warning .. ), that illustrates what i mentioned in this ticket.
With this project, we basically start multiple instances of the same workflow (under src/test/resources/workflows/notifiy-event.bpmn)
This workflow just check the status of the given events, and will put it in cache, and start or stop an alert if appropriate. I voluntary kept it very simple (in our project of course we do things more complicated), just to isolate the parts where activiti is involved.

So, if you run the org.activiti.MyUnitTest, you will see that upon completion it will print you the processing times of workflows for each sets of events.
When I run it on my windows desktop (with Jdk 1.8), I got the following times in ms:
5.17.0
Conditions: events {10000, 75000, 35000}
[8583, 27493, 11978]

5.18.0
Conditions: events {10000, 75000, 35000}
[13530, 55849, 26835]

You can see that 5.18.0 takes more time than 5.17.0, with almost double processing times.

As default, it runs with activiti 5.17.0. To switch to activiti 5.18.0, just update the pom.xml activiti.version properties.

FYI, I configured an h2 in memory database for activiti.


Best Regards,

Mélanie

[melanie1]

Hi Joram,

Do you have any update on this issue? Do you need further details for your investigation ? We would like to migrate to this latest version, but the performances is a showstopper for now.

Thanks and Regards,

Mélanie