• Type: Bug Report
• Resolution: Fixed
• Priority: L3 - Default
• Fix Version/s: 7.6.0, 7.6.0-alpha6
• Affects Version/s: 7.5.4
• Component/s: engine
• Labels:

  • SUPPORT
  • engine

This is the controller panel for Smart Panels app

1. 

   Db2-105_001.png

   189 kB

   01/Nov/16 5:00 PM

2. 

   Db2-105_002.png

   187 kB

   01/Nov/16 5:00 PM

3. 

   Db2-105_003.png

   189 kB

   01/Nov/16 5:00 PM

4. 

   Db2-97_001.png

   225 kB

   01/Nov/16 5:00 PM

5. 

   Db2-97_002.png

   227 kB

   01/Nov/16 5:00 PM

6. HistroyProcessInstanceAuthorizationCheck_SQL_Query.sql

   5 kB

   01/Nov/16 4:56 PM

[CAM-6839] History queries with authorization checks are slow

Collapse comment: Daniel Meyer added a comment - 07/Oct/16 10:08 PM

Daniel Meyer added a comment - 07/Oct/16 10:08 PM

christopher.zell We can have a quick chat about this on tuesday: basically it would mean that we use the join based authorization check for history as well

Expand comment: Daniel Meyer added a comment - 07/Oct/16 10:08 PM

Daniel Meyer added a comment - 07/Oct/16 10:08 PM christopher.zell We can have a quick chat about this on tuesday: basically it would mean that we use the join based authorization check for history as well

Collapse comment: Christopher Kujawa added a comment - 04/Nov/16 9:29 AM, Edited by Christopher Kujawa - 04/Nov/16 9:39 AM

Christopher Kujawa added a comment - 04/Nov/16 9:29 AM - edited

Hi all,

after adding the Authorization Join and reducing the where clause, we have fixed PostgreSQL performance issues and also the Oracle Performance issues.

Following is a list of databases and the historic authorization execution time:

MariaDB: 12,57 sec
MySQL: 14,268 sec
MsSQL: ? (Error lipphardt)
Oracle 12: 16,216 sec
PostgreSQL 93: 15,506 sec
H2: 25,051 sec
Oracle 10: ? (Error lipphardt)
DB2 105: 15,265 sec
DB2 97: 2,992.002 sec

For more details see this table

lipphardt since we have so different executions times, also on different version of databases, i think it will be interesting to execute the performance tests on all databases like the unit tests. Also we have to increase the timeout value since oracle 12 needs 20 mins for the creation of the test data, if the timeout value is below 20 min a timeout error is thrown.

P.S.: It seems that on DB2 9.7 the HistoricActivityInstanceQuery is the Problem not the HistoricProcessInstanceQuery. See this report.

Best regards,
Chris

Expand comment: Christopher Kujawa added a comment - 04/Nov/16 9:29 AM, Edited by Christopher Kujawa - 04/Nov/16 9:39 AM

Christopher Kujawa added a comment - 04/Nov/16 9:29 AM - edited Hi all, after adding the Authorization Join and reducing the where clause, we have fixed PostgreSQL performance issues and also the Oracle Performance issues. Following is a list of databases and the historic authorization execution time: MariaDB : 12,57 sec MySQL : 14,268 sec MsSQL: ? ( Error lipphardt ) Oracle 12 : 16,216 sec PostgreSQL 93 : 15,506 sec H2 : 25,051 sec Oracle 10: ? ( Error lipphardt ) DB2 105 : 15,265 sec DB2 97 : 2,992.002 sec For more details see this table lipphardt since we have so different executions times, also on different version of databases, i think it will be interesting to execute the performance tests on all databases like the unit tests. Also we have to increase the timeout value since oracle 12 needs 20 mins for the creation of the test data, if the timeout value is below 20 min a timeout error is thrown. P.S.: It seems that on DB2 9.7 the HistoricActivityInstanceQuery is the Problem not the HistoricProcessInstanceQuery. See this report . Best regards, Chris

Collapse comment: Christopher Kujawa added a comment - 04/Nov/16 12:56 PM

Christopher Kujawa added a comment - 04/Nov/16 12:56 PM

Fixed the problem with DB2 9.7.

Expand comment: Christopher Kujawa added a comment - 04/Nov/16 12:56 PM

Christopher Kujawa added a comment - 04/Nov/16 12:56 PM Fixed the problem with DB2 9.7 .