Seite nicht gefunden

Object cache

Redis and Memcached remember what WordPress otherwise forgets after every request.

WordPress keeps options, posts, terms and users in memory only for the duration of a single request. With Redis or Memcached they survive it. For that, the kakapo checks at runtime which PHP extension is really loaded, measures the connection with a real write-read cycle and creates the drop-in only after a typed confirmation. If the memory server fails, the site keeps running — just as it did before.

What the object cache offers

Redis or Memcached, depending on the loaded extension

The test writes, reads back, compares, deletes

Drop-in only after typing INSTALLIEREN

A third-party object-cache.php stays untouched

Flushing via the key salt, not via FLUSHDB

Password optionally as a constant in wp-config.php

Here's how it works

Enter host, port and prefix

Test the connection and read the latency

Read the preview, type INSTALLIEREN

FAQ about the object cache

Does my site go down if Redis fails?

It stays reachable. The drop-in then works only in the memory of that one request — exactly as WordPress does without a drop-in, with the database queries from before. The reason for the outage is shown in the admin area.

I already have a plugin with its own object-cache.php.

It is neither overwritten nor deleted. The kakapo recognises a foreign file, names it by name and blocks the write — otherwise the other plugin would be broken afterwards. Remove it first where it came from.

How do I get back?

“Remove drop-in” deletes exactly one file; your settings are kept. No database row and no schedule are left behind, and when the plugin is deactivated the file disappears as well. The entries on the memory server expire by themselves once their lifetime is up.

Object cache

Object cache

What the object cache offers

Here's how it works

FAQ about the object cache

More performance features

Try Performance free for 24 hours.