Hi,

 

we made some SQL level investigations about time consumption of
synchronization task processes. We started with an empty repository and
processed the same external user table (of 5 000 users) twice. First run was
processed more quickly and the time used for SQL operations was divided for
handling of ACT_GE_BYTEARRAY, UAttrValue, ACT_HI_ACTINST, Policy,
SyncopeUser, UAttr and USchema tables. The next run was 150%-200% slower and
DB operations took about 50% of the time. We noticed that almost 75% of DB
operations was used in SELECT query to table ACT_RU_TASK. The exact SQL
clause was "select * from ACT_RU_TASK where PARENT_TASK_ID_ = 'XXXXX'".
There is no index for PARENT_TASK_ID_ column and in our runs the column
value is always null. Is this some kind of bug as it makes updates very
slow?

 

Best regards,

 

Timo

 

Reply via email to