# Redis閰嶇疆鏂囦欢鏍蜂緥

# Note on units: when memory size is needed, it is possible to specifiy
# 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.

# Redis榛樿涓嶆槸浠ュ畧鎶よ繘绋嬬殑鏂瑰紡杩愯锛屽彲浠ラ€氳繃璇ラ厤缃」淇敼锛屼娇鐢▂es鍚敤瀹堟姢杩涚▼
# 鍚敤瀹堟姢杩涚▼鍚庯紝Redis浼氭妸pid鍐欏埌涓€涓猵idfile涓紝鍦�/var/run/redis.pid
daemonize no

# 褰揜edis浠ュ畧鎶よ繘绋嬫柟寮忚繍琛屾椂锛孯edis榛樿浼氭妸pid鍐欏叆/var/run/redis.pid鏂囦欢锛屽彲浠ラ€氳繃pidfile鎸囧畾
pidfile /var/run/redis.pid

# 鎸囧畾Redis鐩戝惉绔彛锛岄粯璁ょ鍙ｄ负6379
# 濡傛灉鎸囧畾0绔彛锛岃〃绀篟edis涓嶇洃鍚琓CP杩炴帴
port 6379

# 缁戝畾鐨勪富鏈哄湴鍧€
# 浣犲彲浠ョ粦瀹氬崟涓€鎺ュ彛锛屽鏋滄病鏈夌粦瀹氾紝鎵€鏈夋帴鍙ｉ兘浼氱洃鍚埌鏉ョ殑杩炴帴
# bind 127.0.0.1
protected-mode no

# Specify the path for the unix socket that will be used to listen for
# incoming connections. There is no default, so Redis will not listen
# on a unix socket when not specified.
#
# unixsocket /tmp/redis.sock
# unixsocketperm 755

# 褰撳鎴风闂茬疆澶氶暱鏃堕棿鍚庡叧闂繛鎺ワ紝濡傛灉鎸囧畾涓�0锛岃〃绀哄叧闂鍔熻兘
timeout 0

# 鎸囧畾鏃ュ織璁板綍绾у埆锛孯edis鎬诲叡鏀寔鍥涗釜绾у埆锛歞ebug銆乿erbose銆乶otice銆亀arning锛岄粯璁や负verbose
# debug (寰堝淇℃伅, 瀵瑰紑鍙戯紡娴嬭瘯姣旇緝鏈夌敤)
# 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 verbose

# 鏃ュ織璁板綍鏂瑰紡锛岄粯璁や负鏍囧噯杈撳嚭锛屽鏋滈厤缃负redis涓哄畧鎶よ繘绋嬫柟寮忚繍琛岋紝鑰岃繖閲屽張閰嶇疆涓烘爣鍑嗚緭鍑猴紝鍒欐棩蹇楀皢浼氬彂閫佺粰/dev/null
# logfile /logs/redis.log

# To enable logging to the system logger, just set 'syslog-enabled' to yes,
# and optionally update the other syslog parameters to suit your needs.
# syslog-enabled no

# Specify the syslog identity.
# syslog-ident redis

# Specify the syslog facility.  Must be USER or between LOCAL0-LOCAL7.
# syslog-facility local0

# 璁剧疆鏁版嵁搴撶殑鏁伴噺锛岄粯璁ゆ暟鎹簱涓�0锛屽彲浠ヤ娇鐢╯elect <dbid>鍛戒护鍦ㄨ繛鎺ヤ笂鎸囧畾鏁版嵁搴搃d
# dbid鏄粠0鍒扳€榙atabases鈥�-1鐨勬暟鐩�
databases 16

################################ SNAPSHOTTING  #################################
# 鎸囧畾鍦ㄥ闀挎椂闂村唴锛屾湁澶氬皯娆℃洿鏂版搷浣滐紝灏卞皢鏁版嵁鍚屾鍒版暟鎹枃浠讹紝鍙互澶氫釜鏉′欢閰嶅悎
# Save the DB on disk:
#
#   save <seconds> <changes>
#
#   Will save the DB if both the given number of seconds and the given
#   number of write operations against the DB occurred.
#
#   婊¤冻浠ヤ笅鏉′欢灏嗕細鍚屾鏁版嵁:
#   900绉掞紙15鍒嗛挓锛夊唴鏈�1涓洿鏀�
#   300绉掞紙5鍒嗛挓锛夊唴鏈�10涓洿鏀�
#   60绉掑唴鏈�10000涓洿鏀�
#   Note: 鍙互鎶婃墍鏈夆€渟ave鈥濊娉ㄩ噴鎺夛紝杩欐牱灏卞彇娑堝悓姝ユ搷浣滀簡

save 900 1
save 300 10
save 60 10000

# 鎸囧畾瀛樺偍鑷虫湰鍦版暟鎹簱鏃舵槸鍚﹀帇缂╂暟鎹紝榛樿涓簓es锛孯edis閲囩敤LZF鍘嬬缉锛屽鏋滀负浜嗚妭鐪丆PU鏃堕棿锛屽彲浠ュ叧闂閫夐」锛屼絾浼氬鑷存暟鎹簱鏂囦欢鍙樼殑宸ㄥぇ
rdbcompression yes

# 鎸囧畾鏈湴鏁版嵁搴撴枃浠跺悕锛岄粯璁ゅ€间负dump.rdb
dbfilename dump.rdb

# 宸ヤ綔鐩綍.
# 鎸囧畾鏈湴鏁版嵁搴撳瓨鏀剧洰褰曪紝鏂囦欢鍚嶇敱涓婁竴涓猟bfilename閰嶇疆椤规寚瀹�
#
# Also the Append Only File will be created inside this directory.
#
# 娉ㄦ剰锛岃繖閲屽彧鑳芥寚瀹氫竴涓洰褰曪紝涓嶈兘鎸囧畾鏂囦欢鍚�
dir ./

################################# REPLICATION #################################

# 涓讳粠澶嶅埗銆備娇鐢╯laveof浠� Redis鏈嶅姟鍣ㄥ鍒朵竴涓猂edis瀹炰緥銆傛敞鎰忥紝璇ラ厤缃粎闄愪簬褰撳墠slave鏈夋晥
# so for example it is possible to configure the slave to save the DB with a
# different interval, or to listen to another port, and so on.
# 璁剧疆褰撴湰鏈轰负slav鏈嶅姟鏃讹紝璁剧疆master鏈嶅姟鐨刬p鍦板潃鍙婄鍙ｏ紝鍦≧edis鍚姩鏃讹紝瀹冧細鑷姩浠巑aster杩涜鏁版嵁鍚屾
# slaveof <masterip> <masterport>


# 褰搈aster鏈嶅姟璁剧疆浜嗗瘑鐮佷繚鎶ゆ椂锛宻lav鏈嶅姟杩炴帴master鐨勫瘑鐮�
# 涓嬫枃鐨勨€渞equirepass鈥濋厤缃」鍙互鎸囧畾瀵嗙爜
# masterauth <master-password>

# When a slave lost the connection with the master, or when the replication
# is still in progress, the slave can act in two different ways:
#
# 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
#    still reply to client requests, possibly with out of data data, or the
#    data set may just be empty if this is the first synchronization.
#
# 2) if slave-serve-stale data is set to 'no' the slave will reply with
#    an error "SYNC with master in progress" to all the kind of commands
#    but to INFO and SLAVEOF.
#
slave-serve-stale-data yes

# Slaves send PINGs to server in a predefined interval. It's possible to change
# this interval with the repl_ping_slave_period option. The default value is 10
# seconds.
#
# repl-ping-slave-period 10

# The following option sets a timeout for both Bulk transfer I/O timeout and
# master data or ping response timeout. The default value is 60 seconds.
#
# It is important to make sure that this value is greater than the value
# specified for repl-ping-slave-period otherwise a timeout will be detected
# every time there is low traffic between the master and the slave.
#
# repl-timeout 60

################################## SECURITY ###################################

# 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.
# 璁剧疆Redis杩炴帴瀵嗙爜锛屽鏋滈厤缃簡杩炴帴瀵嗙爜锛屽鎴风鍦ㄨ繛鎺edis鏃堕渶瑕侀€氳繃auth <password>鍛戒护鎻愪緵瀵嗙爜锛岄粯璁ゅ叧闂�
requirepass 123456
# Command renaming.
#
# It is possilbe to change the name of dangerous commands in a shared
# environment. For instance the CONFIG command may be renamed into something
# of hard to guess so that it will be still available for internal-use
# tools but not available for general clients.
#
# Example:
#
# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
#
# It is also possilbe to completely kill a command renaming it into
# an empty string:
#
# rename-command CONFIG ""

################################### LIMITS ####################################

# 璁剧疆鍚屼竴鏃堕棿鏈€澶у鎴风杩炴帴鏁帮紝榛樿鏃犻檺鍒讹紝Redis鍙互鍚屾椂鎵撳紑鐨勫鎴风杩炴帴鏁颁负Redis杩涚▼鍙互鎵撳紑鐨勬渶澶ф枃浠舵弿杩扮鏁帮紝
# 濡傛灉璁剧疆maxclients 0锛岃〃绀轰笉浣滈檺鍒躲€傚綋瀹㈡埛绔繛鎺ユ暟鍒拌揪闄愬埗鏃讹紝Redis浼氬叧闂柊鐨勮繛鎺ュ苟鍚戝鎴风杩斿洖max Number of clients reached閿欒淇℃伅
# maxclients 128

# Don't use more memory than the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys with an
# EXPIRE set. It will try to start freeing keys that are going to expire
# in little time and preserve keys with a longer time to live.
# Redis will also try to remove objects from free lists if possible.
#
# If all this fails, Redis will start to reply with errors to commands
# that will use more memory, like SET, LPUSH, and so on, and will continue
# to reply to most read-only commands like GET.
#
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
# 'state' server or cache, not as a real DB. When Redis is used as a real
# database the memory usage will grow over the weeks, it will be obvious if
# it is going to use too much memory in the long run, and you'll have the time
# to upgrade. With maxmemory after the limit is reached you'll start to get
# errors for write operations, and this may even lead to DB inconsistency.
# 鎸囧畾Redis鏈€澶у唴瀛橀檺鍒讹紝Redis鍦ㄥ惎鍔ㄦ椂浼氭妸鏁版嵁鍔犺浇鍒板唴瀛樹腑锛岃揪鍒版渶澶у唴瀛樺悗锛孯edis浼氬厛灏濊瘯娓呴櫎宸插埌鏈熸垨鍗冲皢鍒版湡鐨凨ey锛�
# 褰撴鏂规硶澶勭悊鍚庯紝浠嶇劧鍒拌揪鏈€澶у唴瀛樿缃紝灏嗘棤娉曞啀杩涜鍐欏叆鎿嶄綔锛屼絾浠嶇劧鍙互杩涜璇诲彇鎿嶄綔銆�
# Redis鏂扮殑vm鏈哄埗锛屼細鎶奒ey瀛樻斁鍐呭瓨锛孷alue浼氬瓨鏀惧湪swap鍖�
# maxmemory <bytes>

# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
# is reached? You can select among five behavior:
#
# volatile-lru -> remove the key with an expire set using an LRU algorithm
# allkeys-lru -> remove any key accordingly 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 all the kind of policies, Redis will return an error on write
#       operations, when there are not suitable keys for eviction.
#
#       At the date of writing this 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 volatile-lru

# 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

############################## APPEND ONLY MODE ###############################

#
# Note that you can have both the async dumps and the append only file if you
# like (you have to comment the "save" statements above to disable the dumps).
# Still if append only mode is enabled Redis will load the data from the
# log file at startup ignoring the dump.rdb file.
# 鎸囧畾鏄惁鍦ㄦ瘡娆℃洿鏂版搷浣滃悗杩涜鏃ュ織璁板綍锛孯edis鍦ㄩ粯璁ゆ儏鍐典笅鏄紓姝ョ殑鎶婃暟鎹啓鍏ョ鐩橈紝濡傛灉涓嶅紑鍚紝鍙兘浼氬湪鏂數鏃跺鑷翠竴娈垫椂闂村唴鐨勬暟鎹涪澶便€�
# 鍥犱负redis鏈韩鍚屾鏁版嵁鏂囦欢鏄寜涓婇潰save鏉′欢鏉ュ悓姝ョ殑锛屾墍浠ユ湁鐨勬暟鎹細鍦ㄤ竴娈垫椂闂村唴鍙瓨鍦ㄤ簬鍐呭瓨涓€傞粯璁や负no
# IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
# log file in background when it gets too big.

appendonly yes

# 鎸囧畾鏇存柊鏃ュ織鏂囦欢鍚嶏紝榛樿涓篴ppendonly.aof
# appendfilename appendonly.aof

# The fsync() call tells the Operating System to actually write data on disk
# instead to wait for more data in the output buffer. Some OS will really flush
# data on disk, some other OS will just try to do it ASAP.

# 鎸囧畾鏇存柊鏃ュ織鏉′欢锛屽叡鏈�3涓彲閫夊€硷細
# no:琛ㄧず绛夋搷浣滅郴缁熻繘琛屾暟鎹紦瀛樺悓姝ュ埌纾佺洏锛堝揩锛�
# always:琛ㄧず姣忔鏇存柊鎿嶄綔鍚庢墜鍔ㄨ皟鐢╢sync()灏嗘暟鎹啓鍒扮鐩橈紙鎱紝瀹夊叏锛�
# everysec:琛ㄧず姣忕鍚屾涓€娆★紙鎶樿》锛岄粯璁ゅ€硷級

appendfsync everysec
# appendfsync no

# When the AOF fsync policy is set to always or everysec, and a background
# saving process (a background save or AOF log background rewriting) is
# performing a lot of I/O against the disk, in some Linux configurations
# Redis may block too long on the fsync() call. Note that there is no fix for
# this currently, as even performing fsync in a different thread will block
# our synchronous write(2) call.
#
# In order to mitigate this problem it's possible to use the following option
# that will prevent fsync() from being called in the main process while a
# BGSAVE or BGREWRITEAOF is in progress.
#
# This means that while another child is saving the durability of Redis is
# the same as "appendfsync none", that in pratical terms means that it is
# possible to lost up to 30 seconds of log in the worst scenario (with the
# default Linux settings).
#
# 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

# Automatic rewrite of the append only file.
# Redis is able to automatically rewrite the log file implicitly calling
# BGREWRITEAOF when the AOF log size will growth by the specified percentage.
#
# This is how it works: Redis remembers the size of the AOF file after the
# latest rewrite (or if no rewrite happened since the restart, the size of
# the AOF at startup is used).
#
# 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 precentage of zero in order to disable the automatic AOF
# rewrite feature.

auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb

################################## SLOW LOG ###################################

# The Redis Slow Log is a system to log queries that exceeded a specified
# execution time. The execution time does not include the I/O operations
# like talking with the client, sending the reply and so forth,
# but just the time needed to actually execute the command (this is the only
# stage of command execution where the thread is blocked and can not serve
# other requests in the meantime).
#
# You can configure the slow log with two parameters: one tells Redis
# what is the execution time, in microseconds, to exceed in order for the
# command to get logged, and the other parameter is the length of the
# slow log. When a new command is logged the oldest one is removed from the
# queue of logged commands.

# The following time is expressed in microseconds, so 1000000 is equivalent
# to one second. Note that a negative number disables the slow log, while
# a value of zero forces the logging of every command.
slowlog-log-slower-than 10000

# There is no limit to this length. Just be aware that it will consume memory.
# You can reclaim memory used by the slow log with SLOWLOG RESET.
slowlog-max-len 1024

################################ VIRTUAL MEMORY ###############################

### WARNING! Virtual Memory is deprecated in Redis 2.4
### The use of Virtual Memory is strongly discouraged.

### WARNING! Virtual Memory is deprecated in Redis 2.4
### The use of Virtual Memory is strongly discouraged.

# Virtual Memory allows Redis to work with datasets bigger than the actual
# amount of RAM needed to hold the whole dataset in memory.
# In order to do so very used keys are taken in memory while the other keys
# are swapped into a swap file, similarly to what operating systems do
# with memory pages.
# 鎸囧畾鏄惁鍚敤铏氭嫙鍐呭瓨鏈哄埗锛岄粯璁ゅ€间负no锛�
# VM鏈哄埗灏嗘暟鎹垎椤靛瓨鏀撅紝鐢盧edis灏嗚闂噺杈冨皯鐨勯〉鍗冲喎鏁版嵁swap鍒扮鐩樹笂锛岃闂鐨勯〉闈㈢敱纾佺洏鑷姩鎹㈠嚭鍒板唴瀛樹腑
# 鎶妚m-enabled璁剧疆涓簓es锛屾牴鎹渶瑕佽缃ソ鎺ヤ笅鏉ョ殑涓変釜VM鍙傛暟锛屽氨鍙互鍚姩VM浜�
# vm-enabled no
# vm-enabled yes

# This is the path of the Redis swap file. As you can guess, swap files
# can't be shared by different Redis instances, so make sure to use a swap
# file for every redis process you are running. Redis will complain if the
# swap file is already in use.
#
# Redis浜ゆ崲鏂囦欢鏈€濂界殑瀛樺偍鏄疭SD锛堝浐鎬佺‖鐩橈級
# 铏氭嫙鍐呭瓨鏂囦欢璺緞锛岄粯璁ゅ€间负/tmp/redis.swap锛屼笉鍙涓猂edis瀹炰緥鍏变韩
# *** WARNING *** if you are using a shared hosting the default of putting
# the swap file under /tmp is not secure. Create a dir with access granted
# only to Redis user and configure Redis to create the swap file there.
# vm-swap-file /tmp/redis.swap

# With vm-max-memory 0 the system will swap everything it can. Not a good
# default, just specify the max amount of RAM you can in bytes, but it's
# better to leave some margin. For instance specify an amount of RAM
# that's more or less between 60 and 80% of your free RAM.
# 灏嗘墍鏈夊ぇ浜巚m-max-memory鐨勬暟鎹瓨鍏ヨ櫄鎷熷唴瀛橈紝鏃犺vm-max-memory璁剧疆澶氬皯锛屾墍鏈夌储寮曟暟鎹兘鏄唴瀛樺瓨鍌ㄧ殑锛圧edis鐨勭储寮曟暟鎹氨鏄痥eys锛�
# 涔熷氨鏄褰搗m-max-memory璁剧疆涓�0鐨勬椂鍊欙紝鍏跺疄鏄墍鏈塿alue閮藉瓨鍦ㄤ簬纾佺洏銆傞粯璁ゅ€间负0
# vm-max-memory 0

# Redis swap鏂囦欢鍒嗘垚浜嗗緢澶氱殑page锛屼竴涓璞″彲浠ヤ繚瀛樺湪澶氫釜page涓婇潰锛屼絾涓€涓猵age涓婁笉鑳借澶氫釜瀵硅薄鍏变韩锛寁m-page-size鏄鏍规嵁瀛樺偍鐨勬暟鎹ぇ灏忔潵璁惧畾鐨勩€�
# 寤鸿濡傛灉瀛樺偍寰堝灏忓璞★紝page澶у皬鏈€鍚庤缃负32鎴�64bytes锛涘鏋滃瓨鍌ㄥ緢澶х殑瀵硅薄锛屽垯鍙互浣跨敤鏇村ぇ鐨刾age锛屽鏋滀笉纭畾锛屽氨浣跨敤榛樿鍊�
# vm-page-size 32

# 璁剧疆swap鏂囦欢涓殑page鏁伴噺鐢变簬椤佃〃锛堜竴绉嶈〃绀洪〉闈㈢┖闂叉垨浣跨敤鐨刡itmap锛夋槸瀛樻斁鍦ㄥ唴瀛樹腑鐨勶紝鍦ㄧ鐩樹笂姣�8涓猵ages灏嗘秷鑰�1byte鐨勫唴瀛�
# swap绌洪棿鎬诲閲忎负 vm-page-size * vm-pages
#
# With the default of 32-bytes memory pages and 134217728 pages Redis will
# use a 4 GB swap file, that will use 16 MB of RAM for the page table.
#
# It's better to use the smallest acceptable value for your application,
# but the default is large in order to work in most conditions.
# vm-pages 134217728

# Max number of VM I/O threads running at the same time.
# This threads are used to read/write data from/to swap file, since they
# also encode and decode objects from disk to memory or the reverse, a bigger
# number of threads can help with big objects even if they can't help with
# I/O itself as the physical device may not be able to couple with many
# reads/writes operations at the same time.
# 璁剧疆璁块棶swap鏂囦欢鐨処/O绾跨▼鏁帮紝鏈€鍚庝笉瑕佽秴杩囨満鍣ㄧ殑鏍告暟锛屽鏋滆缃负0锛岄偅涔堟墍鏈夊swap鏂囦欢鐨勬搷浣滈兘鏄覆琛岀殑锛屽彲鑳戒細閫犳垚姣旇緝闀挎椂闂寸殑寤惰繜锛岄粯璁ゅ€间负4
# vm-max-threads 4

############################### ADVANCED CONFIG ###############################

# Hashes are encoded in a special way (much more memory efficient) when they
# have at max a given numer of elements, and the biggest element does not
# exceed a given threshold. You can configure this limits with the following
# configuration directives.
# 鎸囧畾鍦ㄨ秴杩囦竴瀹氱殑鏁伴噺鎴栬€呮渶澶х殑鍏冪礌瓒呰繃鏌愪竴涓寸晫鍊兼椂锛岄噰鐢ㄤ竴绉嶇壒娈婄殑鍝堝笇绠楁硶
# hash-max-zipmap-entries 512
# hash-max-zipmap-value 64

# Similarly to hashes, small lists are also encoded in a special way in order
# to save a lot of space. The special representation is only used when
# you are under the following limits:
list-max-ziplist-entries 512
list-max-ziplist-value 64

# Sets have a special encoding in just one case: when a set is composed
# of just strings that happens to be integers in radix 10 in the range
# of 64 bit signed integers.
# The following configuration setting sets the limit in the size of the
# set in order to use this special memory saving encoding.
set-max-intset-entries 512

# Similarly to hashes and lists, sorted sets are also specially encoded in
# order to save a lot of space. This encoding is only used when the length and
# elements of a sorted set are below the following limits:
zset-max-ziplist-entries 128
zset-max-ziplist-value 64

# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
# order to help rehashing the main Redis hash table (the one mapping top-level
# keys to values). The hash table implementation redis uses (see dict.c)
# performs a lazy rehashing: the more operation you run into an hash table
# that is rhashing, the more rehashing "steps" are performed, so if the
# server is idle the rehashing is never complete and some more memory is used
# by the hash table.
#
# The default is to use this millisecond 10 times every second in order to
# active rehashing the main dictionaries, freeing memory when possible.
#
# If unsure:
# use "activerehashing no" if you have hard latency requirements and it is
# not a good thing in your environment that Redis can reply form time to time
# to queries with 2 milliseconds delay.
# 鎸囧畾鏄惁婵€娲婚噸缃搱甯岋紝榛樿涓哄紑鍚�
activerehashing yes

################################## INCLUDES ###################################

# 鎸囧畾鍖呭惈鍏朵粬鐨勯厤缃枃浠讹紝鍙互鍦ㄥ悓涓€涓绘満涓婂涓猂edis瀹炰緥涔嬮棿浣跨敤鍚屼竴浠介厤缃枃浠讹紝鑰屽悓鏃跺悇瀹炰緥鍙堟嫢鏈夎嚜宸辩殑鐗瑰畾閰嶇疆鏂囦欢
# include /path/to/local.conf
# include /path/to/other.conf