Memcached vs Redis

Oct 21, 2014

Obviously, that depends upon usage. Redis can be used for multiple purposes while Memcached seems to be focused on one basic but important function.

Currently, I'm using or testing both as simple cache stores for individual article pages where the key-value is post_id-HTML.

I'm also storing the Grebe homepage within each system too.

I'm using Nginx to access Memcached while I'm using my Grebe Perl code to read the cached pages from Redis.

I need to recompile Nginx to include the Redis module. I'll attempt to do this and then use the Nginx server block config file to pull cached pages from Redis. I'll do simple speed tests to compare diffs.

http://jamieonsoftware.com/post/59738699304/memcached-vs-redis

http://oldblog.antirez.com/post/redis-memcached-benchmark.html

http://redis.io/topics/benchmarks

http://stackoverflow.com/questions/10558465/memcache-vs-redis

Memcached is a volatile in-memory key/value store. Redis can act like one (and do that job as well as memcached), but it is a data structure server.

Benchmarks are often conflicting, but this much is clear: when used like memcached Redis falls somewhere between nearly as fast or maybe even a little faster.

The powerful data types are particularly important. They allow redis to provide a fantastic shared queue (lists), a great messaging solution (pub/sub), a good place for storing sessions (hashes), and a compelling place for high score tracking (sorted sets). These are just a few examples that scratch the surface.

To answer your original question: The performance and memory usage of Redis compared to memcached should be relatively similar. Close enough that for most uses any performance difference in either direction is academic as neither is likely to be the bottleneck.

Values up to 512MB in size (memcached limited to 1MB per key)

#redis - #memcached - #caching