summaryrefslogtreecommitdiff
path: root/redis.conf
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2011-06-25 12:22:03 +0200
committerantirez <antirez@gmail.com>2011-06-25 12:22:03 +0200
commitc9d0c3623a7714bd41a35237f4ba927206a7adb6 (patch)
tree691c04cd364b578f5043ca2bc089a5d333bc737e /redis.conf
parentc1c9d551da6dd534c8dae051a3a7e64bf7db6bfb (diff)
downloadredis-c9d0c3623a7714bd41a35237f4ba927206a7adb6.tar.gz
diskstore removed
Diffstat (limited to 'redis.conf')
-rw-r--r--redis.conf26
1 files changed, 0 insertions, 26 deletions
diff --git a/redis.conf b/redis.conf
index 87d34eef0..6d18e2f58 100644
--- a/redis.conf
+++ b/redis.conf
@@ -312,32 +312,6 @@ no-appendfsync-on-rewrite no
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
-#################################### DISK STORE ###############################
-
-# When disk store is active Redis works as an on-disk database, where memory
-# is only used as a object cache.
-#
-# This mode is good for datasets that are bigger than memory, and in general
-# when you want to trade speed for:
-#
-# - less memory used
-# - immediate server restart
-# - per key durability, without need for backgrond savig
-#
-# On the other hand, with disk store enabled MULTI/EXEC are no longer
-# transactional from the point of view of the persistence on disk, that is,
-# Redis transactions will still guarantee that commands are either processed
-# all or nothing, but there is no guarantee that all the keys are flushed
-# on disk in an atomic way.
-#
-# Of course with disk store enabled Redis is not as fast as it is when
-# working with just the memory back end.
-
-diskstore-enabled no
-diskstore-path redis.ds
-cache-max-memory 0
-cache-flush-delay 0
-
############################### ADVANCED CONFIG ###############################
# Hashes are encoded in a special way (much more memory efficient) when they