Hi! > Ferret is unstable in production. Segfaults, corrupted indexes > galore. We've switched around 40 clients form ferret to sphinx and > solved their problems this way. I will never use ferret again after > all the problems I have seen it cause peoples production apps.
I'd really like anybody experiencing problems like this to contact me or even better the ferret-talk mailing list about such problems. I have several sites using Ferret with DRb server runs rock solid there. I must admit that they're relatively low traffic, but high load is nothing that will make Ferret crash or currupt indexes, if you use it in the right way (say, one process accessing the index). Without doubt there are cases when Ferret will segfault, i.e. because of platform specific problems, poor argument checking and error handling in the C code and so on, but they may be circumvented most of the time. Not nice, but acts_as_ferret already does most of this for you. I also did some load tests with acts_as_ferret's DRb server a while ago, where it handled > 30 mixed indexing and search requests per second from multiple client > processes for hours, and no crash or index corruption (index size was 7GB at the end of the run) happened. So to summarize: it's definitely possible to have a stable Ferret setup, before you take on the work to switch to something else why not drop me a line and I'll be happy to have a look at your problem. However from what I've read here I'll be sure to check out Sphinx soon so I know what you're talking about here ;-) Cheers, Jens --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
