I'm using Ferret/aaf with the DRb server under a medium load at Ravelry.com. I think that we peak at 10-12 queries per second and a little less than 1 update per second.
My biggest problem has been indexing speed. I've been gradually switching over to Sphinx (http://www.sphinxsearch.com/) for indexes that don't have to be updated in realtime (places where I can afford several minutes of lag). Emulating near realtime index updates in Sphinx is a little hacky but I find that it is worth it. Casey On Fri, 25 Jan 2008, Ryan King wrote: > On Jan 25, 2008, at 7:02 AM, John Leach wrote: >> Hi all, >> >> there was a recent thread[1] on rails-deploy about Ferret in which a >> lot >> of people complained of problems using it in production. >> >> I've been using Ferret (with DRb) for many months now with no serious >> issues. I'm assuming the posters know what they're doing so I'm >> guessing they're just using Ferret in higher-scale environments than >> me. >> >> I spoke to someone in person yesterday who claimed that Ferret over >> DRb >> couldn't keep up with their use rate and had been investigating >> replicating the ferret database between two machines. >> >> With all these bad experiences, I'd like to hear about some good >> experiences. Anyone care to comment? Anyone using it under huge >> load? >> Care to provide some numbers and some notes about how you've made it >> work? > > I had used ferret w/ DrB at Technorati on a project that had several > indexes of 5-10M documents. To make it work well I had to limit the > update rates to the index (I think I took it down to about 1-2/s). > > To go to higher updates rates I would have had to change how we were > writing and serving indexes. > > -ryan > _______________________________________________ > 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
