################################ 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.
#
#   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 ""
# 存 DB 到磁盤：
#
#   格式：save <間隔時間（秒）> <寫入次數>
#
#   根據給定的時間間隔和寫入次數將數據保存到磁盤
#
#   下面的例子的意思是：
#   900 秒內如果至少有 1 個 key 的值變化，則保存
#   300 秒內如果至少有 10 個 key 的值變化，則保存
#   60 秒內如果至少有 10000 個 key 的值變化，則保存
#　　
#   注意：你可以注釋掉所有的 save 行來停用保存功能。
#   也可以直接一個空字符串來實現停用：
#   save ""
save 900 1
save 300 10
save 60 10000
# 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.
# 默認情況下，如果 redis 最後一次的後台保存失敗，redis 將停止接受寫操作，
# 這樣以一種強硬的方式讓用戶知道數據不能正確的持久化到磁盤，
# 否則就會沒人注意到災難的發生。
#
# 如果後台保存進程重新啟動工作了，redis 也將自動的允許寫操作。
#
# 然而你要是安裝了靠譜的監控，你可能不希望 redis 這樣做，那你就改成 no 好了。<br># 如果配置成no 那麼表示你不在乎數據的一致性，或者你又其他手段發現合控制。
stop-writes-on-bgsave-error yes
# 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.
# 是否在 dump .rdb 數據庫的時候使用 LZF 壓縮字符串
# 默認都設為 yes
# 如果你希望保存子進程節省點 cpu ，你就設置它為 no ，
# 不過這個數據集可能就會比較大
rdbcompression yes
# 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.
# 是否校驗rdb文件  但是CRC64算法會增大大約10%的性能消耗
rdbchecksum yes
# The filename where to dump the DB
# 設置 dump 文件的默認文件文件名<br>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.
# 工作目錄
# 例如上面的 dbfilename 只指定了文件名，
# 但是它會寫入到這個目錄下。這個配置項一定是個目錄，而不能是文件名。
dir ./