memcache should work (although I think others have had issues with it in the past - depends on the memcache ruby client, perhaps?). I wouldn't get carried away with dealing with equivalent searches - just treat each search query separately, and then you can use them as search keys.
But I've not done any of this myself, so it's just guesswork. If you're on twitter, perhaps ask @gaskopf (Jochen Kächelin): http://twitpic.com/2xrkgs -- Pat On 18/10/2010, at 9:26 AM, badnaam wrote: > What is your general thought on caching? I am using TS for keyword > searches for let's say a Post model where the post body, comments, > title etc are indexed. > > I use memcached for caching objects for not sure what caching > technique is good in this case, where the keywords might change even > though the restults for the keyword remain the same (for example, > "remain same" and "same remain" might yield same results (with "any" > matching) but can't be used as cache keys). > > Right now, my search controller is exposed with no caching and not > very comfortable with that. How does this scale? > > Thanks > > -- > 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. > -- 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.
