First impression with replicated redis cache

  • This is the real deal for speed freaks. Benched it against my favorite disk cache (Hyper Cache) – it’s around 10 times faster. It can work on a separate/remote redis server too.

    Pro: Super fast compared to disk caches (10x faster remote – 20x faster if redis is on localhost).
    -live cache can be replicated to a hot backup
    -despite the release number (v0.8) it is stable and has no issues with anonymous comments. Cache invalidation for post and feeds works nicely (Still need to test the /pages, /tag, /categories – the usual WP stuff…)-
    -Very lightweight and CPU friendly. Open source and well supported.
    -compresses pages in memory
    -low CPU use. Can run on low-end hardware

    Cons: Not every plug likes it. Some cookies (like PHPSESSID) must be excluded to get pages cached.
    -no easy way to change/update cached content by hand. For example, change a sitebar widget and you must flushall your redis database if you run a high TTL. Disk caches lets you grep/sed content much easier.
    -need some free memory (48gb for some 3000 posts).

  • The topic ‘First impression with replicated redis cache’ is closed to new replies.