Likely this is because under the hood when IndexWriter flushes your
deletes, it opens readers. It closes the readers as soon as the
deletes are done, thus creating a fair amount of garbage (which looks
like memory used by the JVM).
How are you measuring the memory usage? Likely it's mostly garba
I was wondering if anybody else that has been using updateDocument
noticed it uses a large amount of memory when updating an existing document.
For example, when using updateDocument on an empty Lucene directory, the
resulting 12K documents creates a 3MB index, the amount of memory the
program
