lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Resolved: (LUCENE-528) Optimization for IndexWriter.addIndexes()
Date Thu, 26 Oct 2006 22:58:18 GMT
     [ ]

Yonik Seeley resolved LUCENE-528.

    Resolution: Fixed
      Assignee: Yonik Seeley  (was: Otis Gospodnetic)

Thanks Ning, I just committed this.
Wish I had had it some time ago :-)

> Optimization for IndexWriter.addIndexes()
> -----------------------------------------
>                 Key: LUCENE-528
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Steven Tamm
>         Assigned To: Yonik Seeley
>            Priority: Minor
>         Attachments: AddIndexes.patch, AddIndexesNoOptimize.patch
> One big performance problem with IndexWriter.addIndexes() is that it has to optimize
the index both before and after adding the segments.  When you have a very large index, to
which you are adding batches of small updates, these calls to optimize make using addIndexes()
impossible.  It makes parallel updates very frustrating.
> Here is an optimized function that helps out by calling mergeSegments only on the newly
added documents.  It will try to avoid calling mergeSegments until the end, unless you're
adding a lot of documents at once.
> I also have an extensive unit test that verifies that this function works correctly if
people are interested.  I gave it a different name because it has very different performance
characteristics which can make querying take longer.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message