topic Re: Performances impact when migrating from 5.17 to 5.18 in Alfresco Archive

Performances impact when migrating from 5.17 to 5.18

melanie1 — Thu, 29 Oct 2015 07:53:00 GMT

Hi,I ve created a post on stackoverflow :http://stackoverflow.com/questions/33397728/activiti-5-18-migration-and-performances-impactsasking 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 proces

Re: Performances impact when migrating from 5.17 to 5.18

jbarrez — Tue, 03 Nov 2015 12:11:06 GMT

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

Re: Performances impact when migrating from 5.17 to 5.18

melanie1 — Tue, 03 Nov 2015 12:27:43 GMT

Hi Joram,

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

Best Regards,

Mélanie

Re: Performances impact when migrating from 5.17 to 5.18

jbarrez — Tue, 03 Nov 2015 14:42:05 GMT

Thanks. Looking forward to investigating what could be it.

Re: Performances impact when migrating from 5.17 to 5.18

melanie1 — Wed, 04 Nov 2015 17:17:37 GMT

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

Re: Performances impact when migrating from 5.17 to 5.18

melanie1 — Wed, 18 Nov 2015 15:43:48 GMT

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