Re: Performance improvements using writer.delete vs reader.delete

2007-08-03 Thread Mark Miller
Heh. I suppose I'll defer to your judgment. In my mind, the simple system to make is to just buffer the adds, buffer the deletes - later apply the adds, apply the deletes (or the reverse). I am sure something in Solr would have a more sophisticated process, but my guess was about what the new L

Re: Performance improvements using writer.delete vs reader.delete

2007-08-03 Thread Mike Klaas
On 3-Aug-07, at 3:27 AM, Mark Miller wrote: Also, IndexWriter probably buffers better than you would. If you buffer a delete with IndexWriter and then add a document that would be removed by that delete right after, when the buffered deletes are flushed, your latest doc will not be removed

Re: Performance improvements using writer.delete vs reader.delete

2007-08-03 Thread Mark Miller
Also, IndexWriter probably buffers better than you would. If you buffer a delete with IndexWriter and then add a document that would be removed by that delete right after, when the buffered deletes are flushed, your latest doc will not be removed. Its unlikely your own buffer system would work

Re: Performance improvements using writer.delete vs reader.delete

2007-08-02 Thread Doron Cohen
Andreas Knecht wrote: > We're considering to use the new IndexWriter.deleteDocuments call rather > than the IndexReader.delete call. Are there any performance > improvements that this may provide, other than the benefit of not having > to switch between readers/writers? > > We've looked at LUCENE

Performance improvements using writer.delete vs reader.delete

2007-08-02 Thread Andreas Knecht
Hi, We're considering to use the new IndexWriter.deleteDocuments call rather than the IndexReader.delete call. Are there any performance improvements that this may provide, other than the benefit of not having to switch between readers/writers? We've looked at LUCENE-565, but there's no cle