README

• Replaces the standard cache handler with Redis.
• Optionally store product view/sales stats in Redis and transfer these via cron from Redis to DB.

Important Notice

Triggers and cache entries are stored in the same Redis database. That means, if you define a maxmemory-policy such as allkeys-lru Redis may evict cache entries or triggers. If a trigger is evicted, this will mean that changes to a record via CMS backend may not clear cache entries related to that entry.

To avoid this problem you MUST configure Redis to use sufficient memory so that entries are never evicted. If need be, use the compression configuration to reduce memory footprint.

Using Redis to Store View/Sales Stats

If you use this option, you must configure it to use a different Redis server than the one you configured for caching. Otherwise clearing the cache would also clear the view and sales statistics stored in Redis.