[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-570) Optimize the o^2 loop in DocumentBuilderIndexedEntity.addWorkToQueue

[Emmanuel Bernard (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bernard updated HSEARCH-570:
-------------------------------------

    Fix Version/s:     (was: 3.3.0.CR1)

3.3 is too short for such a change

> Optimize the o^2 loop in DocumentBuilderIndexedEntity.addWorkToQueue
> --------------------------------------------------------------------
>
>                 Key: HSEARCH-570
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-570
>             Project: Hibernate Search
>          Issue Type: Improvement
>    Affects Versions: 3.2.0.Final, 3.2.1, 3.3.0.Alpha1
>            Reporter: Sanne Grinovero
>
> there's a long-standing comment in the method:
> bq. //TODO with the caller loop we are in a n^2: optimize it using a HashMap for work recognition
> Apparently it has a critical impact in some scenarios: [this forum post|https://forum.hibernate.org/viewtopic.php?f=9&t=1006054] mentions the algorithm "running for days" in a 1000 elements change in a single transaction.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira