Best way to combine fragment and object caching for memcached and Rails

caching, fragment, memcached, ruby, ruby-on-rails

Solution

Evan Weaver's Interlock Plugin solves this problem.

You can also implement something like this yourself easily if you need different behavior, such as more fine grained control. The basic idea is to wrap your controller code in a block that is only actually executed if the view needs that data:

# in FooController#show
@foo_finder = lambda{ Foo.find_slow_stuff }

# in foo/show.html.erb
cache 'foo_slow_stuff' do
  @foo_finder.call.each do 
    ...
  end
end

If you're familiar with the basics of ruby meta programming it's easy enough to wrap this up in a cleaner API of your taste.

This is superior to putting the finder code directly in the view:

- keeps the finder code where developers expect it by convention

- keeps the view ignorant of the model name/method, allowing more view reuse

I think cache_fu might have similar functionality in one of it's versions/forks, but can't recall specifically.

The advantage you get from memcached is directly related to your cache hit rate. Take care not to waste your cache capacity and cause unnecessary misses by caching the same content multiple times. For example, don't cache a set of record objects as well as their html fragment at the same time. Generally fragment caching will offer the best performance, but it really depends on the specifics of your application.

Problem

Lets say you have a fragment of the page which displays the most recent posts, and you expire it in 30 minutes. I'm using Rails here. ``` <% cache("recent_posts", :expires_in => 30.minutes) do %> ... <% end %> ``` Obviously you don't need to do the database lookup to get the most recent posts if the fragment exists, so you should be able to avoid that overhead too. What I'm doing now is something like this in the controller which seems to work: ``` unless Rails.cache.exist? "views/recent_posts" @posts = Post.find(:all, :limit=>20, :order=>"updated_at DESC") end ``` Is this the best way? Is it safe? One thing I don't understand is why the key is "`recent_posts`" for the fragment and "`views/recent_posts`" when checking later, but I came up with this after watching `memcached -vv` to see what it was using. Also, I don't like the duplication of manually entering "`recent_posts`", it would be better to keep that in one place. Ideas?

Original source