I thought query caching is per-request? (thread?) Is there a scenario where sharing the query cache is appropriate?
Godfrey — Sent from Mailbox for iPhone On Wed, Oct 9, 2013 at 9:32 PM, Stewart <[email protected]> wrote: > Hi, > It seems that Active record query caching is all done in memory. This is > fine untill you need to run with unicorn that will have multiple workers > each with their own connection. It would be nice to be able to configure a > query caching backend in the same way active support configures caching in > other parts of rails thus allowing for a shared cache between workers. Is > this functionally worth investigating? Have I missed something in the > source code that already does this? > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/groups/opt_out.
