Sam, It sounds like you need to either find a caching strategy that works for your application's needs, or you'll need to adjust how your data is stored (model or data store). Without knowing more about your performance and business needs I can't really speculate with any confidence.
-- Ashton On Sunday, December 14, 2014 8:54:04 PM UTC-7, Sam Raker wrote: > > I'm (still) pulling tweets from twitter, processing them, and storing them > in CouchDB with hashtags as doc ids, such that if a tweet contains 3 > hashtags, that tweet will be indexed under each of those 3 hashtags. My > application hits CouchDB for the relevant document and uses Cheshire to > convert the resulting string to a map. The map's values consist of a few > string values and an array that consists of all the tweets that contain > that hashtag. The problem is thus with common hashtags: the more tweets > contain a given hashtag, the long that hashtag's "tweets" array will be, > and, additionally, the more often that document will be retrieved from > CouchDB. The likelihood and magnitude of performance hits on my app are > therefore correlated, which is Bad. > > I'm reaching out to you all for suggestions about how best to deal with > this situation. Some way of caching something, somehow? I'm at a loss, but > I want to believe there's a solution. > > > Thanks, > -sam > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
