Comments on: Rails Fragment Cache Expiry http://happygiraffe.net/blog/2006/05/07/rails-fragment-cache-expiry/ Wed, 07 Jan 2009 04:46:09 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Dominic Mitchell http://happygiraffe.net/blog/2006/05/07/rails-fragment-cache-expiry/comment-page-1/#comment-692 Dominic Mitchell Mon, 08 May 2006 21:40:38 +0000 tag:happygiraffe.net:Article268#comment-692 <p>Well, I decided on something a little bit simpler in the end. I’ll see how it goes for now with my new <a href="http://happygiraffe.net/blog/archives/2006/05/08/timedfilestore-plugin-0-1" rel="nofollow">TimedFileStore</a> plugin…</p> Well, I decided on something a little bit simpler in the end. I’ll see how it goes for now with my new TimedFileStore plugin…

]]> By: mike http://happygiraffe.net/blog/2006/05/07/rails-fragment-cache-expiry/comment-page-1/#comment-691 mike Mon, 08 May 2006 00:19:34 +0000 tag:happygiraffe.net:Article268#comment-691 <p>We use a mix of time-based fragment caching (that we essentially borrowed from Typo) and rails_cron for longer running and less frequently needed tasks (it could also do cache expiration). Using the “metafragment” approach you can store anything you can read/write with yaml, so you can store any other needed metadata besides just expiration time. But there is a little more coordination involved.</p> <p>The nice part about rails_cron is that the overhead of starting up rails is done once, but it’s scheduling isn’t as flexible as real cron (can’t say “run at 6am on Sundays”).</p> We use a mix of time-based fragment caching (that we essentially borrowed from Typo) and rails_cron for longer running and less frequently needed tasks (it could also do cache expiration). Using the “metafragment” approach you can store anything you can read/write with yaml, so you can store any other needed metadata besides just expiration time. But there is a little more coordination involved.

The nice part about rails_cron is that the overhead of starting up rails is done once, but it’s scheduling isn’t as flexible as real cron (can’t say “run at 6am on Sundays”).

]]>