On Fri, Jun 08, 2007 at 10:25:07AM -0400, Daniel Einspanjer wrote: > The bootstrap indexing actually ended up taking twice the amount of > time listed below. When there was no index directory and I made the > call to rebuild_index, the ferret_index.log file had these lines in > it: > # Logfile created on Thu Jun 07 08:46:34 -0400 2007 by logger.rb/1.5.2.9 > rebuild index: [] > reindexing model CurrentProgram > reindex model CurrentProgram : 0.00% complete : 25658.57 secs to finish > ... > > when it hit 100%, the following lines appeared: > reindex model CurrentProgram : 99.56% complete : 219.29 secs to finish > Created Ferret index in: > ./script/../config/../config/../index/production/current_program > rebuild index: [["CurrentProgram"]] > reindexing model CurrentProgram > reindex model CurrentProgram : 0.00% complete : 25740.65 secs to finish > reindex model CurrentProgram : 0.95% complete : 26065.95 secs to finish > > > So it looks like for some reason, it performed the rebuild twice. :(
damn, that bug seems to come back from time to time, I'll try to fix this over the weekend. > When I looked at it this morning, it had over 116k files in the > current_program directory. Not the most healthy thing. I ran > CurrentProgram.aaf_index.ferret_index.optimize and it took a few > minutes and fully optimized down to three files. It should optimize the index automatically after re-indexing. > I made the testing patch suggested and am running now. I did not > delete the index directory. The ferret_index.log started out with > these lines: > rebuild index: [["CurrentProgram"]] > reindexing model CurrentProgram > reindex model CurrentProgram : 0.00% complete : 3540.78 secs to finish > reindex model CurrentProgram : 0.95% complete : 3510.69 secs to finish > > So it is a significantly shorter time when it isn't actually adding > the doc to the index. Yeah, looks like it's really the indexing that takes the time. Can you make sure for your testing that nothing else accesses the index while the rebuild runs (i.e. shutdown any mongrels running? Or try aaf trunk and the DRb server which will ensure that by design and for performance measurements is the more realistical scenario anyway. > If you have any further ideas on things to try or any other > information you'd like to collect, please let me know. In the > meantime, I'm going to try out the acts_as_solr plugin since I've had > a bit more experience with tuning solr and see what the indexing > performance on that looks like. >From what I've heard it should be on par with aaf when things are working normal (I guess they don't for some reason in your case). btw, what platform do you run on? Jens -- Jens Krämer webit! Gesellschaft für neue Medien mbH Schnorrstraße 76 | 01069 Dresden Telefon +49 351 46766-0 | Telefax +49 351 46766-66 [EMAIL PROTECTED] | www.webit.de Amtsgericht Dresden | HRB 15422 GF Sven Haubold, Hagen Malessa _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
