summaryrefslogtreecommitdiff
path: root/redis.conf
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2010-02-06 13:39:07 +0100
committerantirez <antirez@gmail.com>2010-02-06 13:39:07 +0100
commit6766f45ef27af7f028dd71b5b1482365995bf314 (patch)
tree87ccb12bc1f0f3c44fc33ab181b4a8471cf52798 /redis.conf
parent3c290b9b52c0db299c630cc508d2620ab3497759 (diff)
downloadredis-6766f45ef27af7f028dd71b5b1482365995bf314.tar.gz
multi bulk requests in redis-benchmark, default fsync policy changed to everysec, added a prefix character for DEBUG logs
Diffstat (limited to 'redis.conf')
-rw-r--r--redis.conf20
1 files changed, 12 insertions, 8 deletions
diff --git a/redis.conf b/redis.conf
index 8b8f34a7d..0f5fe34ef 100644
--- a/redis.conf
+++ b/redis.conf
@@ -158,14 +158,18 @@ appendonly no
# always: fsync after every write to the append only log . Slow, Safest.
# everysec: fsync only if one second passed since the last fsync. Compromise.
#
-# The default is "always" that's the safer of the options. It's up to you to
-# understand if you can relax this to "everysec" that will fsync every second
-# or to "no" that will let the operating system flush the output buffer when
-# it want, for better performances (but if you can live with the idea of
-# some data loss consider the default persistence mode that's snapshotting).
-
-appendfsync always
-# appendfsync everysec
+# The default is "everysec" 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 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.
+#
+# If unsure, use "everysec".
+
+# appendfsync always
+appendfsync everysec
# appendfsync no
################################ VIRTUAL MEMORY ###############################