On 6/8/07, Jens Kraemer <[EMAIL PROTECTED]> wrote: > On Fri, Jun 08, 2007 at 10:25:07AM -0400, Daniel Einspanjer wrote: > damn, that bug seems to come back from time to time, I'll try to fix > this over the weekend.
I saw a couple of other threads mentioning something similar to this so I figured it either wasn't fixed in the version I was working with or it might have been a regression. > > 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 see in the rebuild_index method where it calls optimize, but it certainly didn't seem to fully optimize it at that time. Maybe there was something specific to the case of a newly created index instead of opening an existing one? > > 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? Since this was a bootstrapping test, I had no processes running other than the script\console production from which I issued the rebuild_index command. > Or try aaf trunk and the DRb server which will ensure that by design and > for performance measurements is the more realistical scenario anyway. I'm currently planning on running this as a single instance application because the index will be read only at run time and only used by one or two people at a time. > >From what I've heard it [aas] should be on par with aaf when things are > working normal (I guess they don't for some reason in your case). I've heard the same. The only reason I thought to try it out was because of my prior experience with Solr. > btw, what platform do you run on? This is a windows box connecting to a MSSQL server. (I know.. ick. ;) I did some preliminary testing to make sure that the pagination was working properly since I saw in the list that other people had some difficulties with it. Daniel _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
