I am tilting towards Haystack Xapian solution over django sphinx mainly for two reasons 1) Haystack supports - Solr, Xapian and Whoosh. So in future I can easily migrate from Xapian to Solr as my need grows. 2) Sphinx has slow index update. Updating index takes as much time as building a new one.
My views are based on quick reading of material and opinions on web and not on my experience yet. Once I will try haystack xapian this weekend and let you know. On Jun 19, 10:54 am, Nick Arnett <nick.arn...@gmail.com> wrote: > On Sat, Jun 19, 2010 at 9:21 AM, zweb <traderash...@gmail.com> wrote: > > > (Mysql text search will not work as I use INNODB. Solr is powerful but > > I heard it is very memory hungry and it is in Java. Whoosh is not yet > > as mature as others. So that leaves choice between Django Sphinx and > > Haystack Xapian.) > > I meant to mention that although I'm using InnoDB, I'm storing a copy of the > searchable text in a MyISAM table and using the MySQL search on it. That's > okay for now, but I'm looking for clustering, faceted search and other fancy > stuff. > > I've worked in search-related technology for a long time and I should know > that search performance always demands lots of memory... So I may bite the > bullet and use Solr, after all. I just wish there were a way to trade off > the memory for speed until I'm ready to deploy a real working version. > > Nick -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
