zhuyijun/read-redis
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix tracking table max keys option in redis.conf.

Browse Source
This commit is contained in:
antirez 2020-04-29 18:49:42 +02:00
parent 551fed3169
commit fd8f39a283
1 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
redis.conf
View File

@ -626,20 +626,23 @@ replica-priority 100
# to track the keys fetched by many clients. # to track the keys fetched by many clients.
# #
# For this reason it is possible to configure a maximum fill value for the # For this reason it is possible to configure a maximum fill value for the
# invalidation table. By default it is set to 10%, and once this limit is # invalidation table. By default it is set to 1M of keys, and once this limit
# reached, Redis will start to evict caching slots in the invalidation table # is reached, Redis will start to evict keys in the invalidation table
# even if keys are not modified, just to reclaim memory: this will in turn # even if they were not modified, just to reclaim memory: this will in turn
# force the clients to invalidate the cached values. Basically the table # force the clients to invalidate the cached values. Basically the table
# maximum fill rate is a trade off between the memory you want to spend server # maximum size is a trade off between the memory you want to spend server
# side to track information about who cached what, and the ability of clients # side to track information about who cached what, and the ability of clients
# to retain cached objects in memory. # to retain cached objects in memory.
# #
# If you set the value to 0, it means there are no limits, and all the 16 # If you set the value to 0, it means there are no limits, and Redis will
# millions of caching slots can be used at the same time. In the "stats" # retain as many keys as needed in the invalidation table.
# INFO section, you can find information about the amount of caching slots # In the "stats" INFO section, you can find information about the number of
# used at every given moment. # keys in the invalidation table at every given moment.
# #
# tracking-table-max-fill 10 # Note: when key tracking is used in broadcasting mode, no memory is used
# in the server side so this setting is useless.
#
# tracking-table-max-keys 1000000
################################## SECURITY ################################### ################################## SECURITY ###################################