One more thing, his statement that "why returning 20 documents
would perform any better than returning all of them"
(paraphrased), shows complete ignorance of proper Lucene usage.
R -----Original Message----- From: Robert Engels [] Sent:
Wednesday, June 01, 2005 5:52 PM To: Subject: RE: Lucene vs.
Ruby/Odeum I read his complete article... he still doesn't have
a clue. The opening and closing of the IndexReader's is just
creating garbage which is distorting the memory consumption, and
ruining the performance - it is akin to starting it from the
command-line to perform a search. As you state, the Java memory
consumption will continue to grow until it hits the Xmx until it
even attempts to purge, and even then it may not release the
memory back to the OS. Even small one-time use strings will
eventually show huge memory consumption until the runtime needs
the memory. It is my understanding in reviewing the Lucene code,
is that Lucene caches VERY LITTLE information in memory -
seemingly just the skip table for ter