lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leo Galambos <>
Subject Re: When is a good time to call optimize()
Date Wed, 30 Apr 2003 16:09:18 GMT
It is evergreen of this list, I guess :-).

Nobody can tell you IMHO. You would execute it, when your app is in 
"idle" state and you have changed the index significantly.

I've already implemented an algorithm that does not need any optimize(), 
because the index is optimized automatically (moreover it uses less file 
handles - it is important when your app is under DoS time to time). 
Unfortunately, this solution was implemented in another OSS JAVA search 
engine, and it does not run with Lucene architecture AFAIK. I'm sorry.


Rob Outar wrote:

>The product we are working on allows folks to add files to the index, remove
>files from the index, add/remove fields from/to documents in the index, etc.
>so the index changes quite a bit.  I was calling optimize after someone
>added a file or removed a file but performance was poor.  After how many
>changes should I call optimize?  I have noticed since I stopped calling
>optimize I have TONS of files in my index folder... So I need to perodically
>call optimize to cut down on the number of files... So I am curious what
>other folks are doing.  So if anyone has an opinion/solution I would like to
>hear it.
>To unsubscribe, e-mail:
>For additional commands, e-mail:

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

View raw message