[ https://issues.apache.org/jira/browse/SYNCOPE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò resolved SYNCOPE-408. -------------------------------------------- Resolution: Fixed Patch applied, thanks! 1_1_X: http://svn.apache.org/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 > Components: core > Affects Versions: 1.1.3 > Reporter: Guido Wimmel > Assignee: Francesco Chicchiriccò > Priority: Minor > Fix For: 1.1.4, 1.2.0 > > Attachments: indexes.xml.patch > > > 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 TaskDAO.findToExec() > performs a full scan on all entries of the task table with > DTYPE="NotificationTask" (which could be a large number as all executed tasks > are kept), although only very few tasks are selected (those with executed=0). > Creating an index on task.executed solved this problem; attached is a > corresponding patch against the branch 1.1.X. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira