[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-1019) Profile mass indexer to reduce number of index commits

[Guillaume Smet (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44677#comment-44677 ] 

Guillaume Smet commented on HSEARCH-1019:
-----------------------------------------

Hi Emmanuel and Hardy,

I work with Laurent who reported the problem.

Moving from Lucene 3.3 to 3.4 really makes the difference between having the MassIndexer usable or unusable for us (with our 100k documents).

We forced the use of Lucene 3.3 as a workaround for the moment but I'm pretty sure it's going to hit a lot of applications once people start to move to Hibernate Search 4.

IMHO, we should have the ability to configure a number of documents between each commit on the mass indexer.

Note: we can try snapshots on our application if you need us to test something.

-- 
Guillaume

> Profile mass indexer to reduce number of index commits
> ------------------------------------------------------
>
>                 Key: HSEARCH-1019
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1019
>             Project: Hibernate Search
>          Issue Type: Improvement
>          Components: massindexer
>            Reporter: Hardy Ferentschik
>            Assignee: Sanne Grinovero
>            Priority: Blocker
>             Fix For: 4.1
>
>
> We need to profile the new mass indexer design and try to reduce the number of index commits. Performance of the filesystem based directory declined to a bug fix in Lucene (https://issues.apache.org/jira/browse/LUCENE-3418). Trying to reduce the amount of index commits (and hence fsync calls) might alleviate the performance loss. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira