Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Turbo码先生
redis
提交
fd8f39a2
R
redis
项目概览
Turbo码先生
/
redis
与 Fork 源项目一致
从无法访问的项目Fork
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
R
redis
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
fd8f39a2
编写于
4月 29, 2020
作者:
A
antirez
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Fix tracking table max keys option in redis.conf.
上级
551fed31
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
12 addition
and
9 deletion
+12
-9
redis.conf
redis.conf
+12
-9
未找到文件。
redis.conf
浏览文件 @
fd8f39a2
...
...
@@ -626,20 +626,23 @@ replica-priority 100
# to track the keys fetched by many clients.
#
# For this reason it is possible to configure a maximum fill value for the
# invalidation table. By default it is set to 1
0%, and once this limit is
#
reached, Redis will start to evict caching slot
s in the invalidation table
# even if
keys a
re not modified, just to reclaim memory: this will in turn
# invalidation table. By default it is set to 1
M of keys, and once this limit
#
is reached, Redis will start to evict key
s in the invalidation table
# even if
they we
re not modified, just to reclaim memory: this will in turn
# force the clients to invalidate the cached values. Basically the table
# maximum
fill rat
e is a trade off between the memory you want to spend server
# maximum
siz
e 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
# to retain cached objects in memory.
#
# If you set the value to 0, it means there are no limits, and
all the 16
#
millions of caching slots can be used at the same time. In the "stats"
# I
NFO section, you can find information about the amount of caching slots
#
used
at every given moment.
# If you set the value to 0, it means there are no limits, and
Redis will
#
retain as many keys as needed in the invalidation table.
# I
n the "stats" INFO section, you can find information about the number of
#
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 ###################################
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录