topic Re: Activiti SQL query performance in Alfresco Archive

Activiti SQL query performance

shailendra1 — Wed, 08 Jan 2014 09:41:55 GMT

During one of our performance tuning exercise, we observed that while querying for all variables usingActivity was using following query defined in the xml${limitBefore}select distinct RES.*,VAR.ID_ as VAR_ID_, VAR.NAME_ as VAR_NAME_, VAR.TYPE_ as VAR_TYPE_, VAR.REV_ as VAR_REV_,VAR.PROC_INST_ID_ as

Re: Activiti SQL query performance

shailendra1 — Wed, 08 Jan 2014 14:53:10 GMT

I would appreciate if somebody can help me in this !

Re: Activiti SQL query performance

frederikherema1 — Thu, 09 Jan 2014 10:03:00 GMT

Thanks for reporting this. We are looking into this and have made adjustments to the code. The reason this was introduced was an issue in mssql and row-counts for this (https://github.com/Activiti/Activiti/commit/58993f3e22811ea2c00504697174e8d6effc84aa).

In some circumstances, the distinct was really needed. But after some further investigation and testing (https://github.com/Activiti/Activiti/commit/efdcdf99549456dd9b982b3824940b747d96d4ed - https://github.com/Activiti/Activiti/commit/41108dbb5468562ba942e656694ff173f879e10b) we are pretty sure we can remove the distinct, as the mssql issue is adressed by a db-specific SQL-statement instead (selectTaskWithVariablesByQueryCriteria_mssql_or_db2).

This will be part of the next release (5.15).

Re: Activiti SQL query performance

shailendra1 — Fri, 10 Jan 2014 07:57:39 GMT

Thanks Fred,
Glad to contribute !