Redis features include:
Installing and configuring the Redis software is beyond the scope of this guide. Consult resources such as:
Depending on your installation, you can usually find your Redis configuration in one of the following files:
To optimize the Redis instance for your requirements, you get best results by using a dedicated instance for each session, Commerce cache and FPC.
For sessions, Adobe recommends that you enable persistence to copy Redis data to disk using either of the following persistence options: regular Redis Database Backup (RDB) snapshots, or Append Only File (AOF) persistence logs.
Redis Database Backup (RDB) snapshots store the complete database in a dump file after a given time, when a minimum number of keys have changed since the last save. Use the
save setting inside the
redis.conf file to configure this setting.
Append Only File (AOF) stores each write operation sent to Redis in a journal file. Redis reads this file on restart only and uses it to restore the original dataset.
You can also enable both the RDB and AOF options at the same time. For additional details including the advantages and disadvantages of the persistence options, see the Redis Persistence documentation.
For the cache instance, set up the instance so that it is large enough to store your entire Commerce cache. Size requirements depend on different factors like the number of products and store views. As a starting point, you can use the size of the cache folder on your file system. For example, if the
var/cache folder on your file system is 5 GB, set up your Redis instance with at least 5 GB to start. Persistence is not required for the cache instance because the Commerce cache can be restored. See Redis cache guide.
For performance tuning, you can enable the following settings for asynchronous deletion. These settings do not change the behavior of Redis.
On Redis 6.x and later, you can also add the following value: