Actually, it does not. The only call to index.optimize is in the rebuild_index method. A possible extension for aaf is that index.optimize is called automatically each C insertions, where C is some constant (1000 seems reasonable).
I can only agree with Jan on scalability, at the moment I'm keeping an index of over 700.000 bibliographic records. Searches are instant. Regards, Ewout >Hey Fez, > >the limit of indexed items of ferret (and lucene) shouldn't be in the >thousands but in the millions. I've indexed hundreds of thousands of >documents myself with ferret as well as with lucene and 20.000 is not even >near the limit. Regarding the file-count in the index directory: It seems as >if the index was never optimized. This defragments the chunks into one big >index file. You should investigate why this didn't happen. I did not look >into the aaf code for some time but I think that it should do index >optimization from time to time. > >Cheers, >Jan > > >-- >------------------------------ >http://www.inviado.de - Internetseiten für RAe >http://www.xing.com/profile/Jan_Prill >_______________________________________________ >Ferret-talk mailing list >[email protected] >http://rubyforge.org/mailman/listinfo/ferret-talk _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
