# Redis Configuration File
# When you need to specify when a CI memory size, it is necessary to bring the unit,
# usual format is 1k 5gb 4m etc. Jiang Zi:
#
# 1K => 1000 bytes
# 1KB => 1024 bytes
# 1M => 1000000 bytes
# 1MB => 1024 * 1024 bytes
# 1 g of => 1000000000 bytes
# 1GB => 1024 * 1024 * 1024 bytes
#
# unit is not case sensitive, you can also write 1K 5GB 4M row
################################## INCLUDES ###################################
# Let's say you have a template that can be used as standard in all redis server,
# but for certain server and need some personalized settings,
# you can use include to include some other configuration files, this is for you Very useful.
#
# But be careful Oh, include config rewrite command can not be rewritten
# redis always due to final processing configuration command line as a value, so it is best to include you on the front of this document,
# in order to avoid covering configuration changes at runtime. Instead, you put it in the back (foreigners really long-winded).
#
# The include /path/to/local.conf
# the include /path/to/other.conf
################################ common ################# ####################
# Default redis not run as a daemon, if you want it to run in the background, you put it into a yes.
# When redis run as a daemon, it will write a pid file to /var/run/redis.pid inside.
daemonize no
# When redis running as a daemon, it will default pid file written /var/run/redis.pid inside,
# but here you can formulate its own file location.
pidfile /var/run/redis.pid
# Listening port number, the default is 6379, if you set to 0, redis will listen to any client is not connected to the socket.
port 6379
The maximum number of hold # TCP listening
#
# in a highly concurrent environment, you need to increase this value to avoid the problem of slow client connections.
# Linux kernel will quietly reduced to the value of the / proc / sys / net / core / somaxconn corresponding value,
# so you have to modify these two values in order to reach your expectations.
tcp-backlog 511
# By default, redis connected to the server to listen for client on all available network interfaces.
# If you want to make it on a network interface to listen, then you bind one or more IP IP.
#
# Example, a plurality of IP separated by spaces:
#
# 10.0.0.1 the bind 192.168.1.100
# the bind 127.0.0.1
# Specify the path to the unix socket.
#
# Unixsocket /tmp/redis.sock
# 755 unixsocketperm
# Specify to close the connection (whether it is 0) after how many seconds a client idle
timeout 0
# Tcp heartbeat package.
#
# If set to zero, then sent to the client using tcp acks SO_KEEPALIVE in the absence of communication with the client time.
# This is useful of all, consists of two main reasons:
#
# 1) to prevent the death of peers
# 2) from the Take at The Connection Alive at The Point of View of Network
# Equipment's in at The Middle.
#
# The On Linux, at The specified value (in seconds The) IS at The period Used to the send ACKs.
# Note that to use Close at The Connection at The Double of at The Time IS needed.
# the On OTHER kernels' at The period The depends ON at The Kernel the Configuration.
#
# A Reasonable value for the this the Option IS 60 seconds The.
# recommend a reasonable value is 60 seconds
tcp-keepalive 0
# Define log level.
# Can be the following values:
# Debug (applicable to the development or testing phase)
# verbose (MANY constructions rarely Useful info, But not A Mess like at The Debug Level)
# Notice (for production environments)
# warning (only some important message is recorded)
LogLevel Notice
# Specify the location of the log file
logfile ""
# To log records to the system log, put it into a yes,
# can selectively update the other syslog parameters to meet your requirements
# syslog-enabled no
# Set the identity syslog.
# Syslog-ident redis
# Set the syslog facility, you must be a value between the USER or LOCAL0-LOCAL7.
# Syslog-facility local0
# Set the number of databases.
DB # 0 is the default database, you can select <dbid> command to select a different database on each connector,
# dbid but must be a number between 0 to databasees - a value between. 1
Databases 16
################################ snapshot ################# ###############
#
# DB stored to disk:
#
# format: Save <interval (seconds)> <write count>
#
# according to a given time interval and writing the number of save data to disk
#
# the following example is meant:
the # 900 seconds if at least one value change a key, the stored
# value variation 10 key if at least for 300 seconds, to save
# 60 seconds If there are at least 10,000 key value changes, then save
#
# Note: you can comment out the line to save all of the save function is disabled.
# Can directly be implemented to disable an empty string:
# the Save ""
save 900 1
save 300 10
save 60 10000
# By default, if the last redis background saving failed, redis will stop accepting write operations,
# so in a tough way to let the user know that the data is not correctly persisted to disk,
# otherwise they would have no one noticed disaster happened.
#
# If the background save process is restarted work, redis also will automatically allow a write operation.
#
# However, if you install surveillance fly, you may not want to redis do so, then you changed to no good.
stop-writes-on-bgsave- error yes
# Whether to use LZF compression string when a database dump .rdb
# default are set to yes
# If you want to save the child process save point cpu, you can set it to NO,
# but this will be relatively large data sets may
rdbcompression yes
# Check whether rdb file
rdbchecksum yes
# Set the dump file location
dbfilename dump.rdb
# Working directory
# example above dbfilename specify only the file name,
# but it is written to this directory. This configuration item must be a directory, not a file name.
dir ./
################################# master-slave replication ############## ###################
# Master-slave replication. Use slaveof to make a copy of another instance a redis reids instance.
# Note that this only needs to be configured on the slave.
#
# Slaveof <masterip> <masterport>
# If the master password authentication, here set
# masterauth <master-password>
# When a slave lost contact with the master, or copy an ongoing,
# slave may have two forms:
#
# 1) If yes, slave still answering client requests, but the data returned may be out of date,
# or the data may be empty in the first synchronization time
#
# 2) If no, except when you perform other info than he salveof command,
# Slave will return a "sYNC with master in progress" error ,
#
Slave-serve-STALE the Data-yes
# You can configure a slave entity whether to accept the write operation.
# To store the data for a few brief instances, it may be useful slave by writing operation,
# because the relative terms of the number of resynchronization from master, according to data written to the slave would be easier to be removed.
# But if the client because of a wrong configuration write, may also cause some problems.
#
# From redis version 2.6, the default slaves are read-only.
#
# Note: the Read only slaves are not the Designed to BE Exposed to or untrusted to Clients
# ON at The Internet It's the Just A Protection Layer Against Misuse of at The instance..
# Still A the Read only Slave Exports by default All at The Administrative Commands
# SUCH AS CONFIG, . the DEBUG, and the to Forth a Limited extents SO you CAN Improve
# Security slaves of the using Read only 'the rename-Command' All the Shadow to
# Administrative / Dangerous Commands.
# Note: read-only slaves is not designed to be exposed on the internet to untrusted clients.
# It is just a layer of protection against misuse instance.
slave-read-only yes
# Slaves transmits a ping command to the server within a predefined time interval.
# You can change this time interval. The default is 10 seconds.
#
# Repl-the ping-Slave-period 10
# The following option sets the replication timeout for:
# 设置主从复制过期时间
#
# 1) Bulk transfer I/O during SYNC, from the point of view of slave.
# 2) Master timeout from the point of view of slaves (data, pings).
# 3) Slave timeout from the point of view of masters (REPLCONF ACK pings).
#
# 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-ping-slave-period 大
#
# repl-timeout 60
# Disable TCP_NODELAY on the slave socket after SYNC?
#
# If you select "yes" Redis will use a smaller number of TCP packets and
# less bandwidth to send data to slaves. But this can add a delay for
# the data to appear on the slave side, up to 40 milliseconds with
# Linux kernels using a default configuration.
#
# If you select "no" the delay for data to appear on the slave side will
# be reduced but more bandwidth will be used for replication.
#
# By default we optimize for low latency, but in very high traffic conditions
# or when the master and slaves are many hops away, turning this to "yes" may
# be a good idea.
repl-disable-tcp-nodelay no
# Set the master copy from the capacity size. This is used when the backlog is disconnected slaves
# Buffer slave store data, so when a slave wants to reconnect all the re-synchronization is generally undesirable,
# enough synchronization only partially, only the slave transmission OFF this part of the data loss when connected.
#
# The Replication backlog of The Biggest, The Time The Slave The longer CAN BE
# disconnected and later BE Able to Perform A partial Resynchronization.
The larger this value #, salve can disconnect the connection time is longer.
#
# At The backlog IS only allocated Least Once there IS AT A Slave Connected.
#
# Repl-backlog-size 1MB
# After a master has no longer connected slaves for some time, the backlog
# will be freed. The following option configures the amount of seconds that
# need to elapse, starting from the time the last slave disconnected, for
# the backlog buffer to be freed.
# 在某些时候，master 不再连接 slaves，backlog 将被释放。
#
# A value of 0 means to never release the backlog.
# 如果设置为 0 ，意味着绝不释放 backlog 。
#
# repl-backlog-ttl 3600
# When the master is not working properly, Redis Sentinel will be selected from slaves in a new master,
# The smaller this value is, the priority will be selected, but if it is 0, that means that the slave can not be selected .
#
# The default priority is 100.
slave-priority 100
# It is possible for a master to stop accepting writes if there are less than
# N slaves connected, having a lag less or equal than M seconds.
#
# The N slaves need to be in "online" state.
#
# The lag in seconds, that must be <= the specified value, is calculated from
# the last ping received from the slave, that is usually sent every second.
#
# This option does not GUARANTEES that N replicas will accept the write, but
# will limit the window of exposure for lost writes in case not enough slaves
# are available, to the specified number of seconds.
#
# For example to require at least 3 slaves with a lag <= 10 seconds use:
#
# min-slaves-to-write 3
# min-slaves-max-lag 10
#
# Setting one or the other to 0 disables the feature.
#
# By default min-slaves-to-write is set to 0 (feature disabled) and
# min-slaves-max-lag is set to 10.
################################## Safety############### ####################
# Require clients to issue AUTH <PASSWORD> before processing any other
# 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
# Command renaming.
#
# It is possible to change the name of dangerous commands in a shared
# environment. For instance the CONFIG command may be renamed into something
# hard to guess so that it will still be available for internal-use tools
# but not available for general clients.
#
# Example:
#
# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
#
# It is also possible to completely kill a command by renaming it into
# an empty string:
#
# rename-command CONFIG ""
#
# Please note that changing the name of commands that are logged into the
# AOF file or transmitted to slaves may cause problems.
################################### limit ############## ######################
# 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).
#
# 一旦达到最大限制，redis 将关闭所有的新连接
# 并发送一个‘max number of clients reached’的错误。
#
# maxclients 10000
# If you set this value, when the cached data capacity to achieve this value, redis will be based on your choice
to remove some of the keys # eviction policy.
#
# If redis can not be set according to the policy to remove keys, or the policy 'noeviction',
# redis will begin to respond to a command error, such as set, lpush and so on,
# and continue to respond to a read-only commands such as GET
#
# the this the Option IS usually Useful the when a using Redis AS AN the LRU Cache, or to the SET
# A Hard Memory limit for AN instance (a using at The 'noeviction' Policy).
#
# the WARNING: the If you have have slaves attached to AN instance with maxmemory ON,
# at The size of the Output buffers at The needed to Feed at The slaves are Subtracted
# from at The Used Memory COUNT, SO that Network Problems / resyncs by Will
# not the Trigger Loop the WHERE A Keys are evicted, and in the Output at The Turn
# buffer of slaves is full with DELs of keys evicted triggering the deletion
# of more keys, and so forth until the database is completely emptied.
#
# In short... if you have slaves attached it is suggested that you set a lower
# limit for maxmemory so that there is some free RAM on the system for slave
# output buffers (but this is not needed if the policy is 'noeviction').
#
# 最大使用内存
# maxmemory <bytes>
# Maximum memory strategy, you have five choices.
#
#-Volatile the LRU -> the Remove AN The expire at The key with a using the SET AN LRU algorithm
#-volatile the LRU -> use LRU algorithm removes outdated contain key settings.
AllKeys the LRU-# -> to the Remove the any key at The LRU algorithm accordingly &
# AllKeys-the LRU -> Remove all of the key according to the LRU algorithm.
# Volatile-Random -> Remove A Random Key with AN The expire SET
# AllKeys-Random -> Remove A Random Key, the any Key
# volatile-TTL -> Remove The Key with The Nearest The expire Time (Minor the TTL)
# noeviction -> Don 't The expire AT All, the just return the write the operations ON AN error
# noeviction -> let any key expired, just to write returns an error
#
# Note: with the any of above at The Policies, Redis by Will return the write ON AN error
# 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 noeviction
# LRU and minimal TTL algorithms are not precise algorithms but approximated
# algorithms (in order to save memory), so you can tune it for speed or
# accuracy. For default Redis will check five keys and pick the one that was
# used less recently, you can change the sample size using the following
# configuration directive.
#
# The default of 5 produces good enough results. 10 Approximates very closely
# true LRU but costs a bit more CPU. 3 is very fast but not very accurate.
#
# maxmemory-samples 5
############################## APPEND ONLY MODE ###############################
# By default Redis asynchronously dumps the dataset on disk. This mode is
# good enough in many applications, but an issue with the Redis process or
# a power outage may result into a few minutes of writes lost (depending on
# the configured save points).
#
# The Append Only File is an alternative persistence mode that provides
# much better durability. For instance using the default data fsync policy
# (see later in the config file) Redis can lose just one second of writes in a
# dramatic event like a server power outage, or a single write if something
# wrong with the Redis process itself happens, but the operating system is
# still running correctly.
#
# 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
# The name of the append only file (default: "appendonly.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.
#
# Redis supports three different modes:
#
# no: don't fsync, just let the OS flush the data when it wants. Faster.
# always: fsync after every write to the append only log . Slow, Safest.
# everysec: fsync only one time every second. Compromise.
#
# The default is "everysec", as that's usually the right compromise between
# speed and data safety. It's up to you to understand if you can relax this to
# "no" that will let the operating system flush the output buffer when
# it wants, for better performances (but if you can live with the idea of
# some data loss consider the default persistence mode that's snapshotting),
# or on the contrary, use "always" that's very slow but a bit safer than
# everysec.
#
# 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
# 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". In practical terms, this means that it is
# possible to lose 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 grows by the specified percentage.
#
# This is how it works: Redis remembers the size of the AOF file after the
# latest rewrite (if no rewrite has 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 percentage of zero in order to disable the automatic AOF
# rewrite feature.
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
CONTACT ################################ Scripting ################ ###############
# Max execution time of a Lua script in milliseconds.
#
# If the maximum execution time is reached Redis will log that a script is
# still in execution after the maximum allowed time and will start to
# reply to queries with an error.
#
# When a long running script exceed the maximum execution time only the
# SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
# used to stop a script that did not yet called write commands. The second
# is the only way to shut down the server in the case a write commands was
# already issue by the script but the user don't want to wait for the natural
# termination of the script.
#
# Set it to 0 or a negative value for unlimited execution without warnings.
lua-time-limit 5000
################################ REDIS cluster ################ ###############
#
# enable or disable cluster
# cluster-enabled yes
# Every cluster node has a cluster configuration file. This file is not
# intended to be edited by hand. It is created and updated by Redis nodes.
# Every Redis Cluster node requires a different cluster configuration file.
# Make sure that instances running in the same system does not have
# overlapping cluster configuration file names.
#
# cluster-config-file nodes-6379.conf
# Cluster node timeout is the amount of milliseconds a node must be unreachable
# for it to be considered in failure state.
# Most other internal time limits are multiple of the node timeout.
#
# cluster-node-timeout 15000
# A slave of a failing master will avoid to start a failover if its data
# looks too old.
#
# There is no simple way for a slave to actually have a exact measure of
# its "data age", so the following two checks are performed:
#
# 1) If there are multiple slaves able to failover, they exchange messages
# in order to try to give an advantage to the slave with the best
# replication offset (more data from the master processed).
# Slaves will try to get their rank by offset, and apply to the start
# of the failover a delay proportional to their rank.
#
# 2) Every single slave computes the time of the last interaction with
# its master. This can be the last ping or command received (if the master
# is still in the "connected" state), or the time that elapsed since the
# disconnection with the master (if the replication link is currently down).
# If the last interaction is too old, the slave will not try to failover
# at all.
#
# The point "2" can be tuned by user. Specifically a slave will not perform
# the failover if, since the last interaction with the master, the time
# elapsed is greater than:
#
# (node-timeout * slave-validity-factor) + repl-ping-slave-period
#
# So for example if node-timeout is 30 seconds, and the slave-validity-factor
# is 10, and assuming a default repl-ping-slave-period of 10 seconds, the
# slave will not try to failover if it was not able to talk with the master
# for longer than 310 seconds.
#
# A large slave-validity-factor may allow slaves with too old data to failover
# a master, while a too small value may prevent the cluster from being able to
# elect a slave at all.
#
# For maximum availability, it is possible to set the slave-validity-factor
# to a value of 0, which means, that slaves will always try to failover the
# master regardless of the last time they interacted with the master.
# (However they'll always try to apply a delay proportional to their
# offset rank).
#
# Zero is the only value able to guarantee that when all the partitions heal
# the cluster will always be able to continue.
#
# cluster-slave-validity-factor 10
# Cluster slaves are able to migrate to orphaned masters, that are masters
# that are left without working slaves. This improves the cluster ability
# to resist to failures as otherwise an orphaned master can't be failed over
# in case of failure if it has no working slaves.
#
# Slaves migrate to orphaned masters only if there are still at least a
# given number of other working slaves for their old master. This number
# is the "migration barrier". A migration barrier of 1 means that a slave
# will migrate only if there is at least 1 other working slave for its master
# and so forth. It usually reflects the number of slaves you want for every
# master in your cluster.
#
# Default is 1 (slaves migrate only if their masters remain with at least
# one slave). To disable migration just set it to a very large value.
# A value of 0 can be set but is useful only for debugging and dangerous
# in production.
#
# cluster-migration-barrier 1
# In order to setup your cluster make sure to read the documentation
# available at http://redis.io web site.
################################## 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 128
############################# Event notification ##############################
# Redis can notify Pub/Sub clients about events happening in the key space.
# This feature is documented at http://redis.io/topics/keyspace-events
#
# For instance if keyspace events notification is enabled, and a client
# performs a DEL operation on key "foo" stored in the Database 0, two
# messages will be published via Pub/Sub:
#
# PUBLISH __keyspace@0__:foo del
# PUBLISH __keyevent@0__:del foo
#
# It is possible to select the events that Redis will notify among a set
# of classes. Every class is identified by a single character:
#
# K Keyspace events, published with __keyspace@<db>__ prefix.
# E Keyevent events, published with __keyevent@<db>__ prefix.
# g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
# $ String commands
# l List commands
# s Set commands
# h Hash commands
# z Sorted set commands
# x Expired events (events generated every time a key expires)
# e Evicted events (events generated when a key is evicted for maxmemory)
# A Alias for g$lshzxe, so that the "AKE" string means all the events.
#
# The "notify-keyspace-events" takes as argument a string that is composed
# by zero or multiple characters. The empty string means that notifications
# are disabled at all.
#
# Example: to enable list and generic events, from the point of view of the
# event name, use:
#
# notify-keyspace-events Elg
#
# Example 2: to get the stream of the expired keys subscribing to channel
# name __keyevent@0__:expired use:
#
# notify-keyspace-events Ex
#
# By default all notifications are disabled because most users don't need
# this feature and the feature has some overhead. Note that if you don't
# specify at least one of K or E, no events will be delivered.
notify-keyspace-events ""
############################### ADVANCED CONFIG ###############################
# Hashes are encoded using a memory efficient data structure when they have a
# small number of entries, and the biggest entry does not exceed a given
# threshold. These thresholds can be configured using the following directives.
hash-max-ziplist-entries 512
hash-max-ziplist-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
# HyperLogLog sparse representation bytes limit. The limit includes the
# 16 bytes header. When an HyperLogLog using the sparse representation crosses
# this limit, it is converted into the dense representation.
#
# A value greater than 16000 is totally useless, since at that point the
# dense representation is more memory efficient.
#
# The suggested value is ~ 3000 in order to have the benefits of
# the space efficient encoding without slowing down too much PFADD,
# which is O(N) with the sparse encoding. The value can be raised to
# ~ 10000 when CPU is not a concern, but space is, and the data set is
# composed of many HyperLogLogs with cardinality in the 0 - 15000 range.
hll-sparse-max-bytes 3000
# 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 a hash table
# that is rehashing, 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.
#
# use "activerehashing yes" if you don't have such hard requirements but
# want to free memory asap when possible.
activerehashing yes
# The client output buffer limits can be used to force disconnection of clients
# that are not reading data from the server fast enough for some reason (a
# common reason is that a Pub/Sub client can't consume messages as fast as the
# publisher can produce them).
#
# The limit can be set differently for the three different classes of clients:
#
# normal -> normal clients
# slave -> slave clients and MONITOR clients
# pubsub -> clients subscribed to at least one pubsub channel or pattern
#
# The syntax of every client-output-buffer-limit directive is the following:
#
# client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
#
# A client is immediately disconnected once the hard limit is reached, or if
# the soft limit is reached and remains reached for the specified number of
# seconds (continuously).
# So for instance if the hard limit is 32 megabytes and the soft limit is
# 16 megabytes / 10 seconds, the client will get disconnected immediately
# if the size of the output buffers reach 32 megabytes, but will also get
# disconnected if the client reaches 16 megabytes and continuously overcomes
# the limit for 10 seconds.
#
# By default normal clients are not limited because they don't receive data
# without asking (in a push way), but just after a request, so only
# asynchronous clients may create a scenario where data is requested faster
# than it can read.
#
# Instead there is a default limit for pubsub and slave clients, since
# subscribers and slaves receive data in a push fashion.
#
# Both the hard or the soft limit can be disabled by setting them to zero.
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit slave 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
# Redis calls an internal function to perform many background tasks, like
# closing connections of clients in timeout, purging expired keys that are
# never requested, and so forth.
#
# Not all tasks are performed with the same frequency, but Redis checks for
# tasks to perform accordingly to the specified "hz" value.
#
# By default "hz" is set to 10. Raising the value will use more CPU when
# Redis is idle, but at the same time will make Redis more responsive when
# there are many keys expiring at the same time, and timeouts may be
# handled with more precision.
#
# The range is between 1 and 500, however a value over 100 is usually not
# a good idea. Most users should use the default of 10 and raise this up to
# 100 only in environments where very low latency is required.
hz 10
# When a child rewrites the AOF file, if the following option is enabled
# the file will be fsync-ed every 32 MB of data generated. This is useful
# in order to commit the file to the disk more incrementally and avoid
# big latency spikes.
aof-rewrite-incremental-fsync yes