No nrt-reader opened. My heapdump says that the freeCharBlocks-member of DocumentsWriter is holding >20MB. I must say that I keep the IndexWriter open "forever", which (memorywise) does not seem to be "optimal".
-----Ursprüngliche Nachricht----- Von: Michael McCandless [mailto:luc...@mikemccandless.com] Gesendet: Montag, 16. April 2012 14:56 An: java-user@lucene.apache.org Betreff: Re: IndexWriteConfig ignored? RAM can be used in IndexWriter for other reasons: merge is running, near-real-time reader was opened. The RAMBufferSizeMB only applies to buffered postings (indexed documents) If you turn on IndexWriter's infoStream, do you see output saying it's flushing a new segment because RAM is > 5.0 MB? Mike McCandless http://blog.mikemccandless.com On Mon, Apr 16, 2012 at 4:46 AM, Clemens Wyss <clemens...@mysign.ch> wrote: > We limit the memory consumption of our IndexWriters by setting > RAMBufferSizeMB to 5MB (IndexWriterConfig.setRAMBufferSizeMB). > Inspecting a heapdump unveils that I still have writers wich consume/retain > more than 35MB! > How come? > Any help/advice appreciated > Clemens > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
