And that isn't the case, if I am not calling DeleteDocuments(), I don't see the cost of ApplyDeletes.
On Sat, Oct 20, 2012 at 10:40 PM, Itamar Syn-Hershko <[email protected]>wrote: > The image still didn't go through, but I believe you are hitting this: > https://issues.apache.org/jira/browse/LUCENE-2275 > > On Sat, Oct 20, 2012 at 7:23 PM, Oren Eini (Ayende Rahien) < > [email protected]> wrote: > > > Attached > > > > On Sat, Oct 20, 2012 at 7:17 PM, Simon Svensson <[email protected]> > wrote: > > > >> Hi, > >> > >> I believe that your inline image did not survive the mailing list > >> software. Could you publish it somewhere instead? > >> > >> // Simon > >> > >> > >> On 2012-10-20 19:06, Oren Eini (Ayende Rahien) wrote: > >> > >>> To start with, I already read this: http://wiki.apache.org/lucene-** > >>> java/ImproveIndexingSpeed< > http://wiki.apache.org/lucene-java/ImproveIndexingSpeed> > >>> > >>> I am profiling my Lucene code, and I noticed the following: > >>> > >>> Inline image 1 > >>> > >>> As you can see, applying the deletes takes quite a bit of time. > >>> > >>> I am always assuming that I update the documents in Lucene, so my > >>> process is: > >>> > >>> foreach(var item in items) // dummy code, but useful > >>> { > >>> indexWriter.DeleteDocuments(**new Term("UniqueId", item.Id)); > >>> > >>> indexWriter.AddDocument(item.**ToLuceneDocument()); > >>> } > >>> > >>> Is there a way to avoid the costly ApplyDeletes if it doesn't need to > do > >>> the delete? > >>> > >> > >> > > >
