Hey all, I recently converted our application from search_for_ids to faceted search, and have noticed a potentially deal-breaking performance issue that I wanted to get a second opinion on.
Right now, our index is big enough that in certain situations, a hit to the index takes about .4-.5 seconds. In the non-faceted case, this is undesirable, but workable. However, I recently added 5 facets into the index and noticed that the call to facets actually runs a separate search for every facet. This is pushing performance into the 3s range. Has anyone patched around this issue? Is there a mechanism to get faceted results that doesn't go through the offending populate method? Thanks! Kyle -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en.
