top | item 4774084

Reducing server load with Redis

47 points| gnubardt | 13 years ago |crashlytics.com

10 comments

order

mattparlane|13 years ago

There is nothing specific to MongoDB here.

Also, using appropriate cache headers and putting a Varnish cache in front of the Rack server would be far easier and faster and would also reduce the load on the Rack server itself. Oh, but then I couldn't say I created a DSL...

meritt|13 years ago

There's also nothing specific to Redis here.

HN: Do we really need new articles demonstrating how caching works?

anderse|13 years ago

Calling it a DSL is bit weird to me, it's a single instance method. You'd use the same kind of thing to set the appropriate caching headers for Varnish.

antirez|13 years ago

IMHO this other use of Redis inside Crashlytics, doing heavy use of bitmaps, is more interesting:

http://www.slideshare.net/crashlytics/crashlytics-on-redis-a...

js4all|13 years ago

I totally agree, tracking using bitmaps is something where Redis really shines and it is relevant for nearly every site.

nchuhoai|13 years ago

Leonid is bringing up some good points, but I was always wondering: How do you get to do auto-expiring page-caching.

While Leonid is right that Action Caching with Rails.cache is much easier to do, action caching still lets the request hit the stack, while it does not do so with this proposed solution. Page caching makes the expiration of the cache harder then this solution.

Question: It seems this solution has nearly the ease of action caching, but the performance gain like page caching. Is there a low-level gem/solution available to do something like this?