On Fri, Jul 20, 2007 at 10:49:18AM +0200, Kyle Nord wrote: [..] > > I should have actually re-phrased that, I apologize. > > Long term solution thinking here... What happens when the load gets too > high on the box the index is currently on, is there a way to scale it > horizontally? Besides using certain app servers to access certain > indexes (ie: photos for searching on app003 --> search003), and profiles > app002 --> search 002.
Ah ok, I see :-) First of all - have you already checked if load will ever be too high on a dedicated search box with your expected traffic? You know, premature optimization is the root of all evil ;-) Actually the one-process-per-index thing is only necessary for writing to the index, you can have multiple searchers open on the same physical index. So if you find a way to give multiple servers access to the same physical index (i.e. via NAS) you could run searches from multiple machines, but write access would have to be restricted to one machine. Shared file systems like NFS or samba aren't a good idea for sharing the index. Of course you could also just duplicate your index across machines for faster searching, but then you'll have to take care of syncing it with the master every now and then of course. The stock DRb server doesn't have built in support for any of these distribution scenarios. If searches really are equally distributed between the various indexes putting them on separate machines might be your best option, imho. 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
