v1.5.0
Utilizes the "Global" Redis Keyspace
Removed: Support for the REDIS_HASH configuration value.
Users of amophora-storage-postgres that currently utilize the Redis cache need to be aware of three things.
-
The Redis cache now uses
GET/SETcommands instead of theirHcounterparts. This means items are cached in the database's global keyspace, rather than all under a single hashmap. Users upgrading from a version<1.5.0should delete the old hashmap to avoid wasted persistent memory. -
When first deployed, the cache will be cold. This will result in a higher-than-usual load on the database until the new caching keyspace is populated.
-
Upgrading to
v1.5.0means that Redis's eviction mechanisms can safely been enabled to treat Redis as an LRU cache (as long as the Redis instance/cluster is not shared for any other uses).