Rails 3 has limited built-in support for progressive rendering (or template streaming). It can stream your header, page, and footer when each has completed rendering. This can have a big impact on your pages’ speed. In our case it’s brought our average first response time from 1s to 400ms.
However, this doesn’t go as far as we’d like. In previous versions of songkick.com, we used a plugin that activated module-by-module template streaming. This means that the page streams each module of the page as it is rendered, not just in three big blocks.
This doesn’t seem to be possible in Rails 3 (although it is apparently planned for Rails 4), but with a bit of fiddling we have managed to make it work. It’s currently activated on most pages on www.songkick.com, if you head over there and find a slow page you can watch the page come in a module at a time.
I’m sharing it here both because I thought it might be useful, and because it’s a bit of a hack and I’d like feedback on it.
In the action you want to stream, you can turn on standard Rails 3 streaming with:
def show render :stream => true end
But to enable module by module streaming there are two things to do. First, in your layout:
<% $streaming_output_buffer = @output_buffer %> <%= yield %>
And then in the page template (here
show.html.erb) wrap the entire contents in a block:
<% with_output_buffer($streaming_output_buffer) %> … all of ERB template in here <% end %>
This will cause this ERB template to write to the streaming buffer rather than its own output buffer each time it renders a portion of the page.
You should only add this block in the top level page templates. Don’t put it in partials or whatever, otherwise weird things will happen. Also, if your entire page is a render call to just one other template (say the page just contained one big partial) then you won’t see any benefit, because it’s only this template that streams not recursively called ones.
Told you it was a bit of a hack. Hopefully it will tide us over until Rails 4 implements this properly.