Simulate graph states in the browser

redis.conf 23KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540
  1. # Redis configuration file example
  2. # Note on units: when memory size is needed, it is possible to specify
  3. # it in the usual form of 1k 5GB 4M and so forth:
  4. #
  5. # 1k => 1000 bytes
  6. # 1kb => 1024 bytes
  7. # 1m => 1000000 bytes
  8. # 1mb => 1024*1024 bytes
  9. # 1g => 1000000000 bytes
  10. # 1gb => 1024*1024*1024 bytes
  11. #
  12. # units are case insensitive so 1GB 1Gb 1gB are all the same.
  13. # By default Redis does not run as a daemon. Use 'yes' if you need it.
  14. # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
  15. daemonize no
  16. # When running daemonized, Redis writes a pid file in /var/run/redis.pid by
  17. # default. You can specify a custom pid file location here.
  18. pidfile /var/run/redis.pid
  19. # Accept connections on the specified port, default is 6379.
  20. # If port 0 is specified Redis will not listen on a TCP socket.
  21. port 6379
  22. # If you want you can bind a single interface, if the bind option is not
  23. # specified all the interfaces will listen for incoming connections.
  24. #
  25. # bind 127.0.0.1
  26. # Specify the path for the unix socket that will be used to listen for
  27. # incoming connections. There is no default, so Redis will not listen
  28. # on a unix socket when not specified.
  29. #
  30. # unixsocket /tmp/redis.sock
  31. # unixsocketperm 755
  32. # Close the connection after a client is idle for N seconds (0 to disable)
  33. timeout 0
  34. # Set server verbosity to 'debug'
  35. # it can be one of:
  36. # debug (a lot of information, useful for development/testing)
  37. # verbose (many rarely useful info, but not a mess like the debug level)
  38. # notice (moderately verbose, what you want in production probably)
  39. # warning (only very important / critical messages are logged)
  40. loglevel notice
  41. # Specify the log file name. Also 'stdout' can be used to force
  42. # Redis to log on the standard output. Note that if you use standard
  43. # output for logging but daemonize, logs will be sent to /dev/null
  44. logfile stdout
  45. # To enable logging to the system logger, just set 'syslog-enabled' to yes,
  46. # and optionally update the other syslog parameters to suit your needs.
  47. # syslog-enabled no
  48. # Specify the syslog identity.
  49. # syslog-ident redis
  50. # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
  51. # syslog-facility local0
  52. # Set the number of databases. The default database is DB 0, you can select
  53. # a different one on a per-connection basis using SELECT <dbid> where
  54. # dbid is a number between 0 and 'databases'-1
  55. databases 32
  56. ################################ SNAPSHOTTING #################################
  57. #
  58. # Save the DB on disk:
  59. #
  60. # save <seconds> <changes>
  61. #
  62. # Will save the DB if both the given number of seconds and the given
  63. # number of write operations against the DB occurred.
  64. #
  65. # In the example below the behaviour will be to save:
  66. # after 900 sec (15 min) if at least 1 key changed
  67. # after 300 sec (5 min) if at least 10 keys changed
  68. # after 60 sec if at least 10000 keys changed
  69. #
  70. # Note: you can disable saving at all commenting all the "save" lines.
  71. #
  72. # It is also possible to remove all the previously configured save
  73. # points by adding a save directive with a single empty string argument
  74. # like in the following example:
  75. #
  76. # save ""
  77. save 900 1
  78. save 300 10
  79. save 60 10000
  80. # By default Redis will stop accepting writes if RDB snapshots are enabled
  81. # (at least one save point) and the latest background save failed.
  82. # This will make the user aware (in an hard way) that data is not persisting
  83. # on disk properly, otherwise chances are that no one will notice and some
  84. # distater will happen.
  85. #
  86. # If the background saving process will start working again Redis will
  87. # automatically allow writes again.
  88. #
  89. # However if you have setup your proper monitoring of the Redis server
  90. # and persistence, you may want to disable this feature so that Redis will
  91. # continue to work as usually even if there are problems with disk,
  92. # permissions, and so forth.
  93. stop-writes-on-bgsave-error yes
  94. # Compress string objects using LZF when dump .rdb databases?
  95. # For default that's set to 'yes' as it's almost always a win.
  96. # If you want to save some CPU in the saving child set it to 'no' but
  97. # the dataset will likely be bigger if you have compressible values or keys.
  98. rdbcompression yes
  99. # Since verison 5 of RDB a CRC64 checksum is placed at the end of the file.
  100. # This makes the format more resistant to corruption but there is a performance
  101. # hit to pay (around 10%) when saving and loading RDB files, so you can disable it
  102. # for maximum performances.
  103. #
  104. # RDB files created with checksum disabled have a checksum of zero that will
  105. # tell the loading code to skip the check.
  106. rdbchecksum yes
  107. # The filename where to dump the DB
  108. dbfilename dump.rdb
  109. # The working directory.
  110. #
  111. # The DB will be written inside this directory, with the filename specified
  112. # above using the 'dbfilename' configuration directive.
  113. #
  114. # Also the Append Only File will be created inside this directory.
  115. #
  116. # Note that you must specify a directory here, not a file name.
  117. dir /var/redis
  118. ################################# REPLICATION #################################
  119. # Master-Slave replication. Use slaveof to make a Redis instance a copy of
  120. # another Redis server. Note that the configuration is local to the slave
  121. # so for example it is possible to configure the slave to save the DB with a
  122. # different interval, or to listen to another port, and so on.
  123. #
  124. # slaveof <masterip> <masterport>
  125. # If the master is password protected (using the "requirepass" configuration
  126. # directive below) it is possible to tell the slave to authenticate before
  127. # starting the replication synchronization process, otherwise the master will
  128. # refuse the slave request.
  129. #
  130. # masterauth <master-password>
  131. # When a slave lost the connection with the master, or when the replication
  132. # is still in progress, the slave can act in two different ways:
  133. #
  134. # 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
  135. # still reply to client requests, possibly with out of date data, or the
  136. # data set may just be empty if this is the first synchronization.
  137. #
  138. # 2) if slave-serve-stale data is set to 'no' the slave will reply with
  139. # an error "SYNC with master in progress" to all the kind of commands
  140. # but to INFO and SLAVEOF.
  141. #
  142. slave-serve-stale-data yes
  143. # You can configure a slave instance to accept writes or not. Writing against
  144. # a slave instance may be useful to store some ephemeral data (because data
  145. # written on a slave will be easily deleted after resync with the master) but
  146. # may also cause problems if clients are writing to it because of a
  147. # misconfiguration.
  148. #
  149. # Since Redis 2.6 by default slaves are read-only.
  150. #
  151. # Note: read only slaves are not designed to be exposed to untrusted clients
  152. # on the internet. It's just a protection layer against misuse of the instance.
  153. # Still a read only slave exports by default all the administrative commands
  154. # such as CONFIG, DEBUG, and so forth. To a limited extend you can improve
  155. # security of read only slaves using 'rename-command' to shadow all the
  156. # administrative / dangerous commands.
  157. slave-read-only yes
  158. # Slaves send PINGs to server in a predefined interval. It's possible to change
  159. # this interval with the repl_ping_slave_period option. The default value is 10
  160. # seconds.
  161. #
  162. # repl-ping-slave-period 10
  163. # The following option sets a timeout for both Bulk transfer I/O timeout and
  164. # master data or ping response timeout. The default value is 60 seconds.
  165. #
  166. # It is important to make sure that this value is greater than the value
  167. # specified for repl-ping-slave-period otherwise a timeout will be detected
  168. # every time there is low traffic between the master and the slave.
  169. #
  170. # repl-timeout 60
  171. # The slave priority is an integer number published by Redis in the INFO output.
  172. # It is used by Redis Sentinel in order to select a slave to promote into a
  173. # master if the master is no longer working correctly.
  174. #
  175. # A slave with a low priority number is considered better for promotion, so
  176. # for instance if there are three slaves with priority 10, 100, 25 Sentinel will
  177. # pick the one wtih priority 10, that is the lowest.
  178. #
  179. # However a special priority of 0 marks the slave as not able to perform the
  180. # role of master, so a slave with priority of 0 will never be selected by
  181. # Redis Sentinel for promotion.
  182. #
  183. # By default the priority is 100.
  184. slave-priority 100
  185. ################################## SECURITY ###################################
  186. # Require clients to issue AUTH <PASSWORD> before processing any other
  187. # commands. This might be useful in environments in which you do not trust
  188. # others with access to the host running redis-server.
  189. #
  190. # This should stay commented out for backward compatibility and because most
  191. # people do not need auth (e.g. they run their own servers).
  192. #
  193. # Warning: since Redis is pretty fast an outside user can try up to
  194. # 150k passwords per second against a good box. This means that you should
  195. # use a very strong password otherwise it will be very easy to break.
  196. #
  197. # requirepass <null>
  198. # Command renaming.
  199. #
  200. # It is possible to change the name of dangerous commands in a shared
  201. # environment. For instance the CONFIG command may be renamed into something
  202. # of hard to guess so that it will be still available for internal-use
  203. # tools but not available for general clients.
  204. #
  205. # Example:
  206. #
  207. # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
  208. #
  209. # It is also possible to completely kill a command renaming it into
  210. # an empty string:
  211. #
  212. # rename-command CONFIG ""
  213. ################################### LIMITS ####################################
  214. # Set the max number of connected clients at the same time. By default
  215. # this limit is set to 10000 clients, however if the Redis server is not
  216. # able ot configure the process file limit to allow for the specified limit
  217. # the max number of allowed clients is set to the current file limit
  218. # minus 32 (as Redis reserves a few file descriptors for internal uses).
  219. #
  220. # Once the limit is reached Redis will close all the new connections sending
  221. # an error 'max number of clients reached'.
  222. #
  223. # maxclients 10000
  224. # Don't use more memory than the specified amount of bytes.
  225. # When the memory limit is reached Redis will try to remove keys
  226. # accordingly to the eviction policy selected (see maxmemmory-policy).
  227. #
  228. # If Redis can't remove keys according to the policy, or if the policy is
  229. # set to 'noeviction', Redis will start to reply with errors to commands
  230. # that would use more memory, like SET, LPUSH, and so on, and will continue
  231. # to reply to read-only commands like GET.
  232. #
  233. # This option is usually useful when using Redis as an LRU cache, or to set
  234. # an hard memory limit for an instance (using the 'noeviction' policy).
  235. #
  236. # WARNING: If you have slaves attached to an instance with maxmemory on,
  237. # the size of the output buffers needed to feed the slaves are subtracted
  238. # from the used memory count, so that network problems / resyncs will
  239. # not trigger a loop where keys are evicted, and in turn the output
  240. # buffer of slaves is full with DELs of keys evicted triggering the deletion
  241. # of more keys, and so forth until the database is completely emptied.
  242. #
  243. # In short... if you have slaves attached it is suggested that you set a lower
  244. # limit for maxmemory so that there is some free RAM on the system for slave
  245. # output buffers (but this is not needed if the policy is 'noeviction').
  246. #
  247. # maxmemory <bytes>
  248. # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
  249. # is reached? You can select among five behavior:
  250. #
  251. # volatile-lru -> remove the key with an expire set using an LRU algorithm
  252. # allkeys-lru -> remove any key accordingly to the LRU algorithm
  253. # volatile-random -> remove a random key with an expire set
  254. # allkeys-random -> remove a random key, any key
  255. # volatile-ttl -> remove the key with the nearest expire time (minor TTL)
  256. # noeviction -> don't expire at all, just return an error on write operations
  257. #
  258. # Note: with all the kind of policies, Redis will return an error on write
  259. # operations, when there are not suitable keys for eviction.
  260. #
  261. # At the date of writing this commands are: set setnx setex append
  262. # incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
  263. # sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
  264. # zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
  265. # getset mset msetnx exec sort
  266. #
  267. # The default is:
  268. #
  269. # maxmemory-policy volatile-lru
  270. # LRU and minimal TTL algorithms are not precise algorithms but approximated
  271. # algorithms (in order to save memory), so you can select as well the sample
  272. # size to check. For instance for default Redis will check three keys and
  273. # pick the one that was used less recently, you can change the sample size
  274. # using the following configuration directive.
  275. #
  276. # maxmemory-samples 3
  277. ############################## APPEND ONLY MODE ###############################
  278. # By default Redis asynchronously dumps the dataset on disk. This mode is
  279. # good enough in many applications, but an issue with the Redis process or
  280. # a power outage may result into a few minutes of writes lost (depending on
  281. # the configured save points).
  282. #
  283. # The Append Only File is an alternative persistence mode that provides
  284. # much better durability. For instance using the default data fsync policy
  285. # (see later in the config file) Redis can lose just one second of writes in a
  286. # dramatic event like a server power outage, or a single write if something
  287. # wrong with the Redis process itself happens, but the operating system is
  288. # still running correctly.
  289. #
  290. # AOF and RDB persistence can be enabled at the same time without problems.
  291. # If the AOF is enabled on startup Redis will load the AOF, that is the file
  292. # with the better durability guarantees.
  293. #
  294. # Please check http://redis.io/topics/persistence for more information.
  295. appendonly yes
  296. # The name of the append only file (default: "appendonly.aof")
  297. # appendfilename appendonly.aof
  298. # The fsync() call tells the Operating System to actually write data on disk
  299. # instead to wait for more data in the output buffer. Some OS will really flush
  300. # data on disk, some other OS will just try to do it ASAP.
  301. #
  302. # Redis supports three different modes:
  303. #
  304. # no: don't fsync, just let the OS flush the data when it wants. Faster.
  305. # always: fsync after every write to the append only log . Slow, Safest.
  306. # everysec: fsync only one time every second. Compromise.
  307. #
  308. # The default is "everysec" that's usually the right compromise between
  309. # speed and data safety. It's up to you to understand if you can relax this to
  310. # "no" that will let the operating system flush the output buffer when
  311. # it wants, for better performances (but if you can live with the idea of
  312. # some data loss consider the default persistence mode that's snapshotting),
  313. # or on the contrary, use "always" that's very slow but a bit safer than
  314. # everysec.
  315. #
  316. # More details please check the following article:
  317. # http://antirez.com/post/redis-persistence-demystified.html
  318. #
  319. # If unsure, use "everysec".
  320. # appendfsync always
  321. appendfsync everysec
  322. # appendfsync no
  323. # When the AOF fsync policy is set to always or everysec, and a background
  324. # saving process (a background save or AOF log background rewriting) is
  325. # performing a lot of I/O against the disk, in some Linux configurations
  326. # Redis may block too long on the fsync() call. Note that there is no fix for
  327. # this currently, as even performing fsync in a different thread will block
  328. # our synchronous write(2) call.
  329. #
  330. # In order to mitigate this problem it's possible to use the following option
  331. # that will prevent fsync() from being called in the main process while a
  332. # BGSAVE or BGREWRITEAOF is in progress.
  333. #
  334. # This means that while another child is saving the durability of Redis is
  335. # the same as "appendfsync none", that in practical terms means that it is
  336. # possible to lost up to 30 seconds of log in the worst scenario (with the
  337. # default Linux settings).
  338. #
  339. # If you have latency problems turn this to "yes". Otherwise leave it as
  340. # "no" that is the safest pick from the point of view of durability.
  341. no-appendfsync-on-rewrite no
  342. # Automatic rewrite of the append only file.
  343. # Redis is able to automatically rewrite the log file implicitly calling
  344. # BGREWRITEAOF when the AOF log size will growth by the specified percentage.
  345. #
  346. # This is how it works: Redis remembers the size of the AOF file after the
  347. # latest rewrite (or if no rewrite happened since the restart, the size of
  348. # the AOF at startup is used).
  349. #
  350. # This base size is compared to the current size. If the current size is
  351. # bigger than the specified percentage, the rewrite is triggered. Also
  352. # you need to specify a minimal size for the AOF file to be rewritten, this
  353. # is useful to avoid rewriting the AOF file even if the percentage increase
  354. # is reached but it is still pretty small.
  355. #
  356. # Specify a percentage of zero in order to disable the automatic AOF
  357. # rewrite feature.
  358. auto-aof-rewrite-percentage 100
  359. auto-aof-rewrite-min-size 64mb
  360. ################################ LUA SCRIPTING ###############################
  361. # Max execution time of a Lua script in milliseconds.
  362. #
  363. # If the maximum execution time is reached Redis will log that a script is
  364. # still in execution after the maximum allowed time and will start to
  365. # reply to queries with an error.
  366. #
  367. # When a long running script exceed the maximum execution time only the
  368. # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
  369. # used to stop a script that did not yet called write commands. The second
  370. # is the only way to shut down the server in the case a write commands was
  371. # already issue by the script but the user don't want to wait for the natural
  372. # termination of the script.
  373. #
  374. # Set it to 0 or a negative value for unlimited execution without warnings.
  375. lua-time-limit 5000
  376. ################################## SLOW LOG ###################################
  377. # The Redis Slow Log is a system to log queries that exceeded a specified
  378. # execution time. The execution time does not include the I/O operations
  379. # like talking with the client, sending the reply and so forth,
  380. # but just the time needed to actually execute the command (this is the only
  381. # stage of command execution where the thread is blocked and can not serve
  382. # other requests in the meantime).
  383. #
  384. # You can configure the slow log with two parameters: one tells Redis
  385. # what is the execution time, in microseconds, to exceed in order for the
  386. # command to get logged, and the other parameter is the length of the
  387. # slow log. When a new command is logged the oldest one is removed from the
  388. # queue of logged commands.
  389. # The following time is expressed in microseconds, so 1000000 is equivalent
  390. # to one second. Note that a negative number disables the slow log, while
  391. # a value of zero forces the logging of every command.
  392. slowlog-log-slower-than 10000
  393. # There is no limit to this length. Just be aware that it will consume memory.
  394. # You can reclaim memory used by the slow log with SLOWLOG RESET.
  395. slowlog-max-len 128
  396. ############################### ADVANCED CONFIG ###############################
  397. # Hashes are encoded using a memory efficient data structure when they have a
  398. # small number of entries, and the biggest entry does not exceed a given
  399. # threshold. These thresholds can be configured using the following directives.
  400. hash-max-ziplist-entries 512
  401. hash-max-ziplist-value 64
  402. # Similarly to hashes, small lists are also encoded in a special way in order
  403. # to save a lot of space. The special representation is only used when
  404. # you are under the following limits:
  405. list-max-ziplist-entries 512
  406. list-max-ziplist-value 64
  407. # Sets have a special encoding in just one case: when a set is composed
  408. # of just strings that happens to be integers in radix 10 in the range
  409. # of 64 bit signed integers.
  410. # The following configuration setting sets the limit in the size of the
  411. # set in order to use this special memory saving encoding.
  412. set-max-intset-entries 512
  413. # Similarly to hashes and lists, sorted sets are also specially encoded in
  414. # order to save a lot of space. This encoding is only used when the length and
  415. # elements of a sorted set are below the following limits:
  416. zset-max-ziplist-entries 128
  417. zset-max-ziplist-value 64
  418. # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
  419. # order to help rehashing the main Redis hash table (the one mapping top-level
  420. # keys to values). The hash table implementation Redis uses (see dict.c)
  421. # performs a lazy rehashing: the more operation you run into an hash table
  422. # that is rehashing, the more rehashing "steps" are performed, so if the
  423. # server is idle the rehashing is never complete and some more memory is used
  424. # by the hash table.
  425. #
  426. # The default is to use this millisecond 10 times every second in order to
  427. # active rehashing the main dictionaries, freeing memory when possible.
  428. #
  429. # If unsure:
  430. # use "activerehashing no" if you have hard latency requirements and it is
  431. # not a good thing in your environment that Redis can reply form time to time
  432. # to queries with 2 milliseconds delay.
  433. #
  434. # use "activerehashing yes" if you don't have such hard requirements but
  435. # want to free memory asap when possible.
  436. activerehashing yes
  437. # The client output buffer limits can be used to force disconnection of clients
  438. # that are not reading data from the server fast enough for some reason (a
  439. # common reason is that a Pub/Sub client can't consume messages as fast as the
  440. # publisher can produce them).
  441. #
  442. # The limit can be set differently for the three different classes of clients:
  443. #
  444. # normal -> normal clients
  445. # slave -> slave clients and MONITOR clients
  446. # pubsub -> clients subcribed to at least one pubsub channel or pattern
  447. #
  448. # The syntax of every client-output-buffer-limit directive is the following:
  449. #
  450. # client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
  451. #
  452. # A client is immediately disconnected once the hard limit is reached, or if
  453. # the soft limit is reached and remains reached for the specified number of
  454. # seconds (continuously).
  455. # So for instance if the hard limit is 32 megabytes and the soft limit is
  456. # 16 megabytes / 10 seconds, the client will get disconnected immediately
  457. # if the size of the output buffers reach 32 megabytes, but will also get
  458. # disconnected if the client reaches 16 megabytes and continuously overcomes
  459. # the limit for 10 seconds.
  460. #
  461. # By default normal clients are not limited because they don't receive data
  462. # without asking (in a push way), but just after a request, so only
  463. # asynchronous clients may create a scenario where data is requested faster
  464. # than it can read.
  465. #
  466. # Instead there is a default limit for pubsub and slave clients, since
  467. # subscribers and slaves receive data in a push fashion.
  468. #
  469. # Both the hard or the soft limit can be disabled just setting it to zero.
  470. client-output-buffer-limit normal 0 0 0
  471. client-output-buffer-limit slave 256mb 64mb 60
  472. client-output-buffer-limit pubsub 32mb 8mb 60
  473. ################################## INCLUDES ###################################
  474. # Include one or more other config files here. This is useful if you
  475. # have a standard template that goes to all Redis server but also need
  476. # to customize a few per-server settings. Include files can include
  477. # other files, so use this wisely.
  478. #
  479. # include /path/to/local.conf
  480. # include /path/to/other.conf