> From: Jens Kraemer <[EMAIL PROTECTED]> > Subject: Re: [Ferret-talk] Performance before and after optimization
> On Sat, Nov 03, 2007 at 08:49:17PM +0800, Alex Neth wrote: > [..] >> 2) Can I keep a second index so that it doesn't get locked during >> optimization and then switch to the optimized index? Perhaps the >> index >> is not really locked and it is just using all the CPU? (I am using a >> single CPU server)? > > If you're already indexing in batches, keeping a second read-only > index for > searching is a good idea. rsync is useful to keep the search-index > up to > date in this case. > > To check if CPU usage is a problem, try lowering the optimizing > process' > priority and see how it goes. > Thanks Jens. Any suggestion on how to get a two index solution working with acts_as_ferret? I could not find an easy way to change the index location dynamically. I would love to have a "read-only" index. It seems like using rsync might be problematic though as the index might not be in a consistent state throughout the sync. It's not the CPU. The index is definitely locked for reading during optimization. With cheap disk space, I would rather use two indexes, add new records to the "off" index, optimize it, then switch indexes - and go back and for like that. _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
