Units单位:
# Redis configuration file example
# Note on units: when memory size is needed, it is possible to specify
# it in the usual form of 1k 5GB 4M and so forth:
#
# 1k => 1000 bytes
# 1kb => 1024 bytes
# 1m => 1000000 bytes
# 1mb => 1024*1024 bytes
# 1g => 1000000000 bytes
# 1gb => 1024*1024*1024 bytes
#
# units are case insensitive so 1GB 1Gb 1gB are all the same.
1、配置大小单位,开头定义了一些基本的度量单位,只支持bytes,不支持bit
2、对大小写不敏感
################################ GENERAL (通用)##############################
# On Windows, daemonize and pidfile are not supported.
# However, you can run redis as a Windows service, and specify a logfile.
# The logfile will contain the pid.
# Accept connections on the specified port, default is 6379.
# If port 0 is specified Redis will not listen on a TCP socket.
port 6379
在这里指定端口号
# TCP listen() backlog.
#
# In high requests-per-second environments you need an high backlog in order
# to avoid slow clients connections issues. Note that the Linux kernel
# will silently truncate it to the value of /proc/sys/net/core/somaxconn so
# make sure to raise both the value of somaxconn and tcp_max_syn_backlog
# in order to get the desired effect.
tcp-backlog 511
tcp-backlog其实是一个连接队列,backlog队列总和=未完成的三次握手队列+已完成的三次握手队列。在高并发情况下,需要一个高backlog值来避免慢客户端连接问题。注意Linux内核会将这个值减小到/proc/sys/net/core/somaxconn的值,所以需要确认增大somaxconnn和tccp_max_syn_backlog两个值来达到想要的效果。
# Specify the server verbosity level.
# This can be one of:
# debug (a lot of information, useful for development/testing)
# verbose (many rarely useful info, but not a mess like the debug level)
# notice (moderately verbose, what you want in production probably)
# warning (only very important / critical messages are logged)
loglevel notice
reids的四个日志级别:debug verbose notice warning
# Set the number of databases. The default database is DB 0, you can select
# a different one on a per-connection basis using SELECT
# dbid is a number between 0 and 'databases'-1
databases 16
Redis默认右16个数据库
# Compress string objects using LZF when dump .rdb databases?
# For default that's set to 'yes' as it's almost always a win.
# If you want to save some CPU in the saving child set it to 'no' but
# the dataset will likely be bigger if you have compressible values or keys.
rdbcompression yes
是否启用LZF压缩算法。
# Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
# This makes the format more resistant to corruption but there is a performance
# hit to pay (around 10%) when saving and loading RDB files, so you can disable it
# for maximum performances.
#
# RDB files created with checksum disabled have a checksum of zero that will
# tell the loading code to skip the check.
rdbchecksum yes
在存储数据快照后,还可以redis使用CRC64算法来进行数据校验,但是这样会增大大约10%的性能消耗,如果希望获取最大的性能提升,可以关闭此功能。
# The filename where to dump the DB
dbfilename dump.rdb
数据快照存储的文件
# The working directory.
#
# The DB will be written inside this directory, with the filename specified
# above using the 'dbfilename' configuration directive.
#
# The Append Only File will also be created inside this directory.
#
# Note that you must specify a directory here, not a file name.
dir ./
数据快照文件存放的地址 可以使用config get dir命令获得
################################ SNAPSHOTTING (快照)##########################
# Save the DB on disk:
#
# save
#
# Will save the DB if both the given number of seconds and the given
# number of write operations against the DB occurred.
#
# In the example below the behaviour will be to save:
# after 900 sec (15 min) if at least 1 key changed
# after 300 sec (5 min) if at least 10 keys changed
# after 60 sec if at least 10000 keys changed
#
# Note: you can disable saving completely by commenting out all "save" lines.
#
# It is also possible to remove all the previously configured save
# points by adding a save directive with a single empty string argument
# like in the following example:
#
#save "" 禁用指令
save 900 1 15min改了1次
save 300 10 5分钟改了10次
save 60 10000 1分钟1改了10000次
save 秒数 写操作次数
# By default Redis will stop accepting writes if RDB snapshots are enabled
# (at least one save point) and the latest background save failed.
# This will make the user aware (in a hard way) that data is not persisting
# on disk properly, otherwise chances are that no one will notice and some
# disaster will happen.
#
# If the background saving process will start working again Redis will
# automatically allow writes again.
#
# However if you have setup your proper monitoring of the Redis server
# and persistence, you may want to disable this feature so that Redis will
# continue to work as usual even if there are problems with disk,
# permissions, and so forth.
stop-writes-on-bgsave-error yes
如果配置成no,表示不在乎数据不一致性或者有其他手段发现和控制
################################## SECURITY (安全)#############################
# Require clients to issueAUTH
# commands. This might be useful in environments in which you do not trust
# others with access to the host running redis-server.
#
# This should stay commented out for backward compatibility and because most
# people do not need auth (e.g. they run their own servers).
#
# Warning: since Redis is pretty fast an outside user can try up to
# 150k passwords per second against a good box. This means that you should
# use a very strong password otherwise it will be very easy to break.
#
# requirepass foobared
requirepass zuo159951
在这里设置密码
################################### LIMITS (限制)###########################
# Set the max number of connected clients at the same time. By default
# this limit is set to 10000 clients, however if the Redis server is not
# able to configure the process file limit to allow for the specified limit
# the max number of allowed clients is set to the current file limit
# minus 32 (as Redis reserves a few file descriptors for internal uses).
#
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'.
#
# maxclients 10000
客户端最大连接量
# 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 noeviction
缓存过期策略(五种)
volatile-lru:使用LUR算法移除key,只对设置了过期时间的键
allkeys-lru:使用LUR算法移除key
volatile-random:在过期集合中移除随机key,只对设置了过期时间的键。
allkeys-random:移除随机的key
volatile-ttl :移除那些TTL值最小的key,及那些最近要过期的key
noeviction :不进行移除。针对写操作,只是返回错误信息。
# LRU and minimal TTL algorithms are not precise algorithms but approximated
# algorithms (in order to save memory), so you can select as well the sample
# size to check. For instance for default Redis will check three keys and
# pick the one that was used less recently, you can change the sample size
# using the following configuration directive.
#
#maxmemory-samples 3
maxmemory-samples设置样本数量,LRU算法和最小TTL都并非是精确的算法,而是估算值,所以你可以设置样本的大小。redis会默认检查这么多个key并选择其中LUR的那个。
#############################APPEND ONLY MOD(追加)#########################
# AOF and RDB persistence can be enabled at the same time without problems.
# If the AOF is enabled on startup Redis will load the AOF, that is the file
# with the better durability guarantees.
#
# Please check http://redis.io/topics/persistence for more information.
appendonly no
打开AOF持久化则改为yes
# The name of the append only file (default: "appendonly.aof")
appendfilename "appendonly.aof" 文件名称
# More details please check the following article:
# http://antirez.com/post/redis-persistence-demystified.html
#
# If unsure, use "everysec".
# appendfsync always
appendfsync everysec
# appendfsync no
always 同步持久化,每次发生数据变更会被立即记录到磁盘,性能较差但数据完整性比较好
everysec 默认推荐,异步操作,每秒记录,如果一秒内宕机,有数据丢失。
# If you have latency problems turn this to "yes". Otherwise leave it as
# "no" that is the safest pick from the point of view of durability.
no-appendfsync-on-rewrite no
重写时是否运用Appendfsync,用默认no即可,保证数据安全性。
# This base size is compared to the current size. If the current size is
# bigger than the specified percentage, the rewrite is triggered. Also
# you need to specify a minimal size for the AOF file to be rewritten, this
# is useful to avoid rewriting the AOF file even if the percentage increase
# is reached but it is still pretty small.
#
# Specify a percentage of zero in order to disable the automatic AOF
# rewrite feature.
auto-aof-rewrite-percentage 100 上次aof文件的一倍
auto-aof-rewrite-min-size 64mb 当aof文件达到64M时。(工作3G起步)
总结:
常 见配置redis.conf介 绍参数说明
redis.conf 配置项说明如下:
1. Redis默认不是以守护进程的方式运行,可以通过该配置项修改,使用yes启用守护进程daemonize no
2.当Redis以守护进程方式运行时,Redis默认会把pid写入/var/run/redis.pid文件, 可以通过pidfile指定pidfile /var/run/redis.pid
3.指定Redis监听端口,默认端口为6379.为什么选用6379作为默认端口,因为6379在手机按键上MERZ对应的号码,而MERZ取自意大利歌女Alessia Merz的名字port 6379
4.绑定的主机地址bind 127.0.0.1
5.当客户端闲置多长时间后关闭连接,如果指定为0,表示关闭该功能timeout 300
6.指定日志记录级别,Redis总 共支持四个级别。debug、 verbose. notice、 warning, 默认为verboseloglevel verbose
7.日志记录方式。默认为标准输出,如果配置Redis为守护进程方式运行,而这里又配置为日志记录方式为标准输出,则日志将会发送给/dev/nulllogfile stdout
8.设置数据库的数量,默认数据库为0,可以使用SELECT
9.指定在多长时间内,有多少次更新操作,就将数据同步到数据文件。可以多个条件配合save
Redis默认配置文件中提供了三个条件。
save 900 1
save 300 10
save 60 10000
分别表示900秒(15分钟)内有1个更改,300秒(5分钟)内有10个更改以及60秒内有10000个更改。
10.指定存储至本地数据库时是否压缩数据,默认为yes, Redis采用LZF压缩,如果为了节省CPU时间,可以关闭该选项,但会导致数据库文件变的巨大 rdbcompression yes
11.指定本地数据库文件名,默认值为dump.rdbdbfilename dump.rdb
12.指定本地数据库存放目录 dir./
13.设置当本机为Slav服务时,设置master服务的IP地址及端口,在Redis启动时,它会自动从master进行数据同步slaveof
14.当master服务设置了密码保护时,slav服务连接master的密码masterauth
15.设置Redis连接密码,如果配置了连接密码,客户端在连接Redis时需要通过AUTH
16.没置同一时间最大客户端连接数,默认无限制、Redis可 以同吋打开的客戸端连接数为Redis进程可以打开的最大文件描述符数,如果设置maxclients 0,表示不作限制.当客户端连接数到达限制时,Redis会关闭新的连接并向客戸端返回max number of clients reached错误信息
maxclients 128
17.指定Redis最大内存限制. Redls在启动时会把数据加载到内存中,达到最大内存后. Redis会先尝试清除已到期或即将到期的Key.当此方法处理后.仍然到达最大内存设置,将无法再进行写入操作,但仍然可以迸行读取操作。Redis新的vm机制, 会把Key存放内存,Value会存放在swap区
maxmemory
18.指定是否在每次更新操作后进行日志记录,Redis在默人情况下是异步的把数据写入磁盘,如果不开启,可能会在断电时导致一段时间内的数据丢失。因为redis本身同步数据文件是按上面save条件来同步的.所以有的数据会在一段时间内只存在于内存中。 默认为no
appendonly no
19.指定更新日志文件名,默认为appendonly.aof
appendfilename appendonly.aof
20.指定更新日志条件,共有3个可选值:
no:表示等操作系统进行数据缓存同步到磁盘(快)
always:表示每次更新操作后手动调用fsync()将数据写到磁盘(慢,安全)
everysec:表示每秒同步一次 (折衷,默认值)
appendfsync everysec
21.指定是否启用虚拟内存机制,默认值为no,简单的介绍一下, VM机制将数据分页存放,由Redis将 访问量较少的页即冷数据swap到磁盘上,访问多的页面由磁盘自动换出到内存中
vm-enabled no
22.虚拟内存文件路径,默认值为/tmp/redis.swap,不可多个Redis实例共享
vm-swap-file /tmp/redis.swap
23.将所有大于vm max -memory的数据存入虚拟内存,无论vm-max .memory设置多小,所有索引数据都是内存存储的(Redis的索引数据就是keys),也就是说,当vm-max-memory设置为0的时候,其实是所有value都存在于磁盘。默认值为0
vm-max-memory 0
24. Redis swap文件分成了很多的page,一个对象可以保存在多个page上面, 但一个page上不能被多个对象共享,vm-page-size是要根据存储的数据大小来设定的,作者建议如果存储很多小对象,page大小最好设置为32或者64bytes;如果存储很大大对象,则可以使用更大的page,如果不确定,就使用默认值
vm-page-size 32
25.设置swap文件中的page数量,由于页表(一种表示页面空闲或使用的bitmap)是在放在内存中的,在磁盘上每8个pages将消耗1byte的内存。
vm-pages 134217728
26.设置访问swap文件的线程数,最好不要超过机器的核数,如果设置为0,那么所有对swap文件的操作都是串行的,可能会造成比较长时间的延迟。默认值为4
vm-max- threads 4
27.设置在向客户端应答时,是否把较小的包合并为一个包发送,默认为开启glueoutputbuf yes
28.指定在超过一定的数量或者最大的元素超过某一临界值时,采用一种特殊的哈希算法
hash-max-zipmap-entries 64
hash-max-zipmap-value 512
29.指定是否激活重置哈希,默认为开启(后面在介绍Redis的哈希算法时具体绍)
activerehashing yes
30.指定包含其它的配置文件,可以在同一主机上多个Redis实例之间使用同一份配置文件,而同时各个实例又拥有自己的特定配置文件include /path/to/local.conf