Speed and caching1 min readUpdated

Redis for Magento cache and sessions

Two Redis instances, one database and prefix per shop, and a one-click switch back to files.

Magento stores on Gen2 keep their cache in Redis by default. Redis is memory: much faster than files and lighter on the disk.

Magento tab: Varnish on top, Cache and sessions below with the Redis databases of this shop.
Magento tab: Varnish on top, Cache and sessions below with the Redis databases of this shop.

How it is set up

InstancePortBehaviour
Cache6379When memory is full it drops the least used keys. Nothing is written to disk.
Sessions6380Never drops anything and writes to disk, so carts and logins survive a full memory or a restart.

Each shop gets its own database numbers and its own key prefix (id_prefix), so two stores on the same server never mix their cache, and flushing one never empties the other.

Switch to files and back

The Use files button moves cache and sessions back to files, for example while debugging an extension. Use Redis moves them back. Both edit app/etc/env.php for you.

Flushing the cache from the Actions tab empties only this shop's databases.

Did this solve it? If not, tell us what you see and we look at your server.

Open a ticket

Still stuck? Ask a person.

Tickets go straight to the engineers who run ShopWhizzy servers. Tell us the store, what you see and when it started, and we take it from there.