... | ... | @@ -75,6 +75,29 @@ Hier zu suche in der `redis.conf` Datei nach der `maxmemory` Einstellung. Die `r |
|
|
maxmemory 1000mb
|
|
|
|
|
|
|
|
|
# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
|
|
|
# is reached. You can select among five behaviors:
|
|
|
#
|
|
|
# volatile-lru -> remove the key with an expire set using an LRU algorithm
|
|
|
# allkeys-lru -> remove any key according to the LRU algorithm
|
|
|
# volatile-random -> remove a random key with an expire set
|
|
|
# allkeys-random -> remove a random key, any key
|
|
|
# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
|
|
|
# noeviction -> don't expire at all, just return an error on write operations
|
|
|
#
|
|
|
# Note: with any of the above policies, Redis will return an error on write
|
|
|
# operations, when there are no suitable keys for eviction.
|
|
|
#
|
|
|
# At the date of writing these commands are: set setnx setex append
|
|
|
# incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
|
|
|
# sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
|
|
|
# zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
|
|
|
# getset mset msetnx exec sort
|
|
|
#
|
|
|
# The default is:
|
|
|
#
|
|
|
maxmemory-policy allkeys-lru
|
|
|
|
|
|
```
|
|
|
|
|
|
Zusätzlich empfehlen wir die `maxmemory-policy` des Redis Servers anzupassen. Standardmäßig steht die policy auf `noeviction`. Diese Einstellung besagt, falls der Redis Cache kein Speicher mehr zur Verfügung hat, das auch kein weiterer Cache mehr angelegt wird.
|
... | ... | |