Re: IndexWriter.optimize and memory usage

2004-12-03 Thread Paul Elschot
On Friday 03 December 2004 08:43, Paul Elschot wrote: > On Friday 03 December 2004 07:50, Chris Hostetter wrote: ... > > So, If I'm understanding you (and the javadocs) correctly, the real key > > here is maxMergeDocs.  It seems like addDocument will never merge a > > segment untill maxMergeDocs ha

Re: IndexWriter.optimize and memory usage

2004-12-02 Thread Paul Elschot
On Friday 03 December 2004 07:50, Chris Hostetter wrote: > > : See IndexWriter javadoc and in particular mergeFactor, minMergeDocs, > : and maxMergeDocs. This will let you control the size of your segments, > : the frequency of segment merges, the amount of buffered Documents in > : RAM between s

Re: IndexWriter.optimize and memory usage

2004-12-02 Thread Chris Hostetter
: See IndexWriter javadoc and in particular mergeFactor, minMergeDocs, : and maxMergeDocs. This will let you control the size of your segments, : the frequency of segment merges, the amount of buffered Documents in : RAM between segment merges and such. Also, you ask about calling Yeah, I'm fam

Re: IndexWriter.optimize and memory usage

2004-12-02 Thread Otis Gospodnetic
Hello and quick answers: See IndexWriter javadoc and in particular mergeFactor, minMergeDocs, and maxMergeDocs. This will let you control the size of your segments, the frequency of segment merges, the amount of buffered Documents in RAM between segment merges and such. Also, you ask about calli

IndexWriter.optimize and memory usage

2004-12-02 Thread Chris Hostetter
I've been running into an interesting situation that I wanted to ask about. I've been doing some testing by building up indexes with code that looks like this... IndexWriter writer = null; try { writer = new IndexWriter("index", new StandardAnalyzer(), true); writer.m