3 ms·

Thanks getsat for the shout out. Our guys have put in a lot of work adding features and keeping delayed_job up to snuff. I do have to disagree with you on Thin

Thanks getsat for the shout out. Our guys have put in a lot of work adding features and keeping delayed_job up to snuff. I do have to disagree with you on ThinkingSphinx. I have used both, and I gel much better with Solr. Don't get me wrong, the guy(s) who did ThinkingSphinx have worked hard. I just don't like the moving pieces of ThinkingSphinx: continuous rake tasks, the fact that it sits directly on top of the database, extra re-deployment steps when using capistrano. I prefer having the search server sitting apart.

gtani 16y ago
Sphinx does have the advantage that it runs fine on a little 256 Meg VPS, where you're not going to shoehorn in Tomcat or Jetty
- getsat 16y ago
  This and Sphinx's insanely fast indexing speed are two of the main reasons I like it so much. Java is a huge dependency in my opinion. Different strokes for different folks. :)
  - gtani 16y ago
    Yeah, i would say insanely fast indexing speed is a winner at 3 stages of a) developing the 2 or 3 indexes you need for good search results b) running test suites c) production That said, in the past, I haven't been able to transfer the index configuration from sphinx to SOLR indexes and get 98% matches between the 2 engines. Sphinx (thinking sphinx in rails) used to do funny stuff in the pre-1.0, like if you put in 2 search terms you would get X results, if you put in those 2 terms plus another, you would get more results. I think they've fixed most of that in 1.0