這兩年Redis火得可以，Redis也常常被當(dāng)作Memcached的挑戰(zhàn)者被提到桌面上來(lái)。關(guān)于Redis與Memcached的比較更是比比皆是。然而，Redis真的在功能、性能以及內(nèi)存使用效率上都超越了Memcached嗎？

下面內(nèi)容來(lái)自Redis作者在stackoverflow上的一個(gè)回答，對(duì)應(yīng)的問(wèn)題是《Is memcached a dinosaur in comparison to Redis?》（相比Redis，Memcached真的過(guò)時(shí)了嗎？）

• You should not care too much about performances. Redis is faster per core with small values, but memcached is able to use multiple cores with a single executable and TCP port without help from the client. Also memcached is faster with big values in the order of 100k. Redis recently improved a lot about big values (unstable branch) but still memcached is faster in this use case. The point here is: nor one or the other will likely going to be your bottleneck for the query-per-second they can deliver.
• 沒(méi)有必要過(guò)多的關(guān)心性能，因?yàn)槎叩男阅芏家呀?jīng)足夠高了。由于Redis只使用單核，而Memcached可以使用多核，所以在比較上，平均每一個(gè)核上Redis在存儲(chǔ)小數(shù)據(jù)時(shí)比Memcached性能更高。而在100k以上的數(shù)據(jù)中，Memcached性能要高于Redis，雖然Redis最近也在存儲(chǔ)大數(shù)據(jù)的性能上進(jìn)行優(yōu)化，但是比起Memcached，還是稍有遜色。說(shuō)了這么多，結(jié)論是，無(wú)論你使用哪一個(gè)，每秒處理請(qǐng)求的次數(shù)都不會(huì)成為瓶頸。（比如瓶頸可能會(huì)在網(wǎng)卡）
• You should care about memory usage. For simple key-value pairs memcached is more memory efficient. If you use Redis hashes, Redis is more memory efficient. Depends on the use case.
• 如果要說(shuō)內(nèi)存使用效率，使用簡(jiǎn)單的key-value存儲(chǔ)的話，Memcached的內(nèi)存利用率更高，而如果Redis采用hash結(jié)構(gòu)來(lái)做key-value存儲(chǔ)，由于其組合式的壓縮，其內(nèi)存利用率會(huì)高于Memcached。當(dāng)然，這和你的應(yīng)用場(chǎng)景和數(shù)據(jù)特性有關(guān)。
• You should care about persistence and replication, two features only available in Redis. Even if your goal is to build a cache it helps that after an upgrade or a reboot your data are still there.
• 如果你對(duì)數(shù)據(jù)持久化和數(shù)據(jù)同步有所要求，那么推薦你選擇Redis，因?yàn)檫@兩個(gè)特性Memcached都不具備。即使你只是希望在升級(jí)或者重啟系統(tǒng)后緩存數(shù)據(jù)不會(huì)丟失，選擇Redis也是明智的。
• You should care about the kind of operations you need. In Redis there are a lot of complex operations, even just considering the caching use case, you often can do a lot more in a single operation, without requiring data to be processed client side (a lot of I/O is sometimes needed). This operations are often as fast as plain GET and SET. So if you don’t need just GEt/SET but more complex things Redis can help a lot (think at timeline caching).
• 當(dāng)然，最后還得說(shuō)到你的具體應(yīng)用需求。Redis相比Memcached來(lái)說(shuō)，擁有更多的數(shù)據(jù)結(jié)構(gòu)和并支持更豐富的數(shù)據(jù)操作，通常在Memcached里，你需要將數(shù)據(jù)拿到客戶端來(lái)進(jìn)行類似的修改再set回去。這大大增加了網(wǎng)絡(luò)IO的次數(shù)和數(shù)據(jù)體積。在Redis中，這些復(fù)雜的操作通常和一般的GET/SET一樣高效。所以，如果你需要緩存能夠支持更復(fù)雜的結(jié)構(gòu)和操作，那么Redis會(huì)是不錯(cuò)的選擇。

來(lái)源：Is memcached a dinosaur in comparison to Redis?（其他人的回答同樣值得一看）