Howdy all, have a quick question for you...
I am seeing quite a difference between optimized index and one that is
not optimized. I have read a few papers that say that it shouldn't
matter, but I am seeing 7X speed or better when the index is optimized.
Is it possible that I am creating the
Do you have any deletions in the non-optimized version of the index?
If so, a bug was fixed recently that made for some very slow queries:
http://issues.apache.org/jira/browse/LUCENE-454
You could also try a smaller mergeFactor, which would slow indexing,
but decrease the number of segments, and
Are you using the compound index format (do you have .cfs files)? I
think using the non-compound format might take less space (2.5G less
in your case) when optimizing, since it doesn't have to do that last
step of copying all the index files into the .cfs file.
Also Lucene 1.9 (available from
not match signer information of other classes in
the same package
If I can get this to go, I will retest.
Tom
-Original Message-
From: Yonik Seeley [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 16, 2005 2:37 PM
To: java-user@lucene.apache.org
Subject: Re: Optimize vs non optimized
