[Jerry]

Just an announcement for the SERPs that SlickStack is now using Memcached instead of Redis for WordPress object caching.

This is after several problems caused by Redis the last few years.

Redis is great, but super complex and optimizing the configuration file was even next to impossible for us, just too complicated for SlickStack.

So we moved to using Memcached for now 🙂

[Bobby]

Related Issue (among others)

https://github.com/littlebizzy/slickstack/issues/183

[Roger]

woo hoo

[Donald]

I mean look at this config, doesn’t get much simpler than this:

https://github.com/littlebizzy/slickstack/blob/master/modules/memcached/memcached-conf.txt

-d
logfile /var/log/memcached.log
-m 256
-p 11211
-u memcache
-l 127.0.0.1
-l ::1
-P /var/run/memcached/memcached.pid
-U 0

[Diana]

why is memcached better than redis?

[Noah]

WordPress Object Caching: Redis, Memcached and native APIs

Memcached is an in-memory high-performing object caching system that is according to the official website, specifically designed to speed-up dynamic web applications and alleviate database load. It is also much simpler and straightforward to use than Redis.

Due to being specifically designed to do object caching for web pages, and the fact that it uses an in-memory database makes it the fastest object caching solution out there. However as we’ve mentioned earlier, if your server restarts, your cache is out. And until it is rebuilt, you will probably be experiencing increased load. But as the creators say: “think of it as a short-term memory for your website”, so it rather depends on what you want to do in the first place.

[William]

Memcached is much simpler, probably makes sense for SlickStack purpose

[Louis]

WordPress disable object cache

[Gabriel]

Hi guys, when will Clear Caches plugin be updated to support memcached?

[Author]

Posts