[
https://issues.apache.org/jira/browse/SYNCOPE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729351#comment-13729351
]
Hudson commented on SYNCOPE-408:
--------------------------------
SUCCESS: Integrated in Syncope-1_1_X #95 (See
[https://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
> --------------------------
>
> 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
