lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aigner, Thomas" <>
Subject RE: Optimize vs non optimized index
Date Wed, 16 Nov 2005 22:17:10 GMT
Thanks for the advice Yonik.. I do have deletions in my 1.4.3 index. I
downloaded the lucene-1.9-rc1-dev.jar file to give it a go and after
upgrading a few of the methods from the deprecated methods, I keep
getting this error: class "org.apache.lucene.document.Field$Store"'s
signer information does not match signer information of other classes in
the same package

If I can get this to go, I will retest.

-----Original Message-----
From: Yonik Seeley [] 
Sent: Wednesday, November 16, 2005 2:37 PM
Subject: Re: Optimize vs non optimized index

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:

You could also try a smaller mergeFactor, which would slow indexing,
but decrease the number of segments, and hence speed searching.

Now hiring --

On 11/16/05, Aigner, Thomas <> wrote:
> 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
> Is it possible that I am creating the original index incorrectly?
> The reason why I am asking it due to the space it takes to optimize an
> index.  I have an index that takes up about 2.5G, but when I optimize
> it, it will take an additional 5G of space to do this (so 7.5G to
> optimize it).  I was wondering if perhaps if this is the norm or not.
> Thanks ahead of time,
> Tom

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message