/r1510390
trunk: http://svn.apache.org/r1510392
Add index on task.executed
--
Key: SYNCOPE-408
URL: https://issues.apache.org/jira/browse/SYNCOPE-408
Project: Syncope
Issue Type: Improvement
://builds.apache.org/job/Syncope-trunk/286/])
[SYNCOPE-408] Merge from 1_1_X (ilgrosso: rev 1510392)
* /syncope/trunk
* /syncope/trunk/core/src/main/resources/indexes.xml
Add index on task.executed
--
Key: SYNCOPE-408
URL
://builds.apache.org/job/Syncope-1_1_X/95/])
[SYNCOPE-408] Applying provided patch, successfully tested against all
supported databases (ilgrosso: rev 1510390)
* /syncope/branches/1_1_X/core/src/main/resources/indexes.xml
Add index on task.executed
[
https://issues.apache.org/jira/browse/SYNCOPE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guido Wimmel updated SYNCOPE-408:
-
Attachment: indexes.xml.patch
Add index on task.executed
Guido Wimmel created SYNCOPE-408:
Summary: Add index on task.executed
Key: SYNCOPE-408
URL: https://issues.apache.org/jira/browse/SYNCOPE-408
Project: Syncope
Issue Type: Improvement
Hi,
in our Syncope installation (1.1.3 on Tomcat/MySQL) we observed long execution
times (1s) for TaskDAO.findToExec(),
which is called periodically from NotificationJob to determine which
notifications should be sent.
According to our analysis, this is due to the fact that
Hi,
in our Syncope installation (1.1.3 on Tomcat/MySQL) we observed long
execution times (1s) for TaskDAO.findToExec(),
which is called periodically from NotificationJob to determine which
notifications should be sent.
According to our analysis, this is due to the fact that