Advanced caching in Rails
broadcastingadam.com
Advanced caching in Rails
1–10 of 21 posts
Re: Advanced caching in Rails
#2> hash = {:this => {:is => 'a hash'}}
> Rails.cache.write 'complicated-object', object
change hash for object, or viceversa
Re: Advanced caching in Rails
#3Re: Advanced caching in Rails
#4The post is actually easy to read and understand. Funny thing is, in the last couple of weeks, there has been a lot of material (podcasts, posts, screencast, etc) on the subject. But it didn't really take off until 37signals mentioned it.
Re: Advanced caching in Rails
#5The post is actually easy to read and understand. Funny thing is, in the last couple of weeks, there has been a lot of material (podcasts, posts, screencast, etc) on the subject. But it didn't really take off until 37signals mentioned it.
I believe this is the first time it has made it to HN. I've always gotten very good feedback on it. Thanks for your comments.
Re: Advanced caching in Rails
#6Re: Advanced caching in Rails
#7Re: Advanced caching in Rails
#8The post is actually easy to read and understand. Funny thing is, in the last couple of weeks, there has been a lot of material (podcasts, posts, screencast, etc) on the subject. But it didn't really take off until 37signals mentioned it.
Is there any screencast other than the Railscasts one?
Re: Advanced caching in Rails
#9My Rails sites spend 85% of the time generating HTML, the other 15% of the time is spent communicating with the db and other external services. And it's not easy to figure out where the slowness is. When I've ran performance profiles in the past, something like 50% of the time was spent in GC.
Re: Advanced caching in Rails
#10All the time spent talking about caching in Rails avoids the real issue: generating complex html in Ruby/Rails is really slow . My Rails sites spend 85% of the time generating HTML, the other 15% of the time is spent communicating with the db and other external services. And it's not easy to figure out where the slowness is. When I've ran performance profiles in the past, something like 50% of the time was spent in G…
One thing worth mentioning: anecdotally I've found that ActiveRecord can have an impact on performance far beyond the cost of the database queries, both by directly adding a reasonable amount of overhead and by instantiating a lot of objects internally which in turn triggers a lot of garbage collection. I wouldn't be surprised if that accounts for a fair chunk of what you're seeing.