One Redis database for each website

Our previous change to the how Redis flushes cache had an impact on servers hosting a lot of websites. Previously, when a single website requested a flush of the Redis cache, it would result in the entire database being emptied. As a result, this caused spikes in server load as other websites attempted to write cache to the Redis database simultaneously.

However, we have now implemented a new approach where each website is assigned its own separate Redis database. This change improves performance over time by ensuring that each website can operate independently without affecting others on the server.