28 lines
1.2 KiB
Plaintext
28 lines
1.2 KiB
Plaintext
|
# redis.conf
|
||
|
|
|
||
|
|
# The 'maxmemory' directive controls the maximum amount of memory Redis is allowed to use.
|
||
|
|
# Setting 'maxmemory 0' means there is no limit on memory usage, allowing Redis to use as much
|
||
|
|
# memory as the operating system allows. This is suitable for environments where memory
|
||
|
|
# constraints are not a concern.
|
||
|
|
#
|
||
|
|
# Alternatively, you can specify a limit, such as 'maxmemory 15gb', to restrict Redis to
|
||
|
|
# using a maximum of 15 gigabytes of memory.
|
||
|
|
#
|
||
|
|
# Example:
|
||
|
|
# maxmemory 0 # Unlimited memory usage
|
||
|
|
# maxmemory 15gb # Limit memory usage to 15 GB
|
||
|
|
|
||
|
|
maxmemory 0
|
||
|
|
|
||
|
|
# This setting determines how Redis evicts keys when it reaches the memory limit.
|
||
|
|
# `allkeys-lru` evicts the least recently used keys from all keys stored in Redis,
|
||
|
|
# allowing frequently accessed data to remain in memory while older data is removed.
|
||
|
|
# That said we use `volatile-lru` as Redis is used both as a cache and processing
|
||
|
|
# queue in self-hosted Sentry.
|
||
|
|
# > The volatile-lru and volatile-random policies are mainly useful when you want to
|
||
|
|
# > use a single Redis instance for both caching and for a set of persistent keys.
|
||
|
|
# > However, you should consider running two separate Redis instances in a case like
|
||
|
|
# > this, if possible.
|
||
|
|
|
||
|
|
maxmemory-policy volatile-lru
|