multi bulk requests in redis-benchmark, default fsync policy changed to everysec...

[redis.git] / redis.conf

diff --git a/redis.conf b/redis.conf
index 8b8f34a7d05ae4ea63975728a36ca7ada3ca7da3..0f5fe34efd886abef1a199571b16542cbd17bf92 100644 (file)
--- 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 ###############################