max zipmap entries and max zipmap value parameters added into INFO output

[redis.git] / redis.conf

diff --git a/redis.conf b/redis.conf
index f675ac203143716e2c02a17467e9afa6bc175e0e..0ed593d2446f0a3222cf7c8bde8a3d3f931db186 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.
 #
 # 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 ###############################
 # appendfsync no
 
 ################################ VIRTUAL MEMORY ###############################


@@ -182,15 +186,32 @@ appendfsync always
 vm-enabled no
 # vm-enabled yes
 
 vm-enabled no
 # vm-enabled yes
 

+# This is the path of the Redis swap file. As you can guess, swap files
+# can't be shared by different Redis instances, so make sure to use a swap
+# file for every redis process you are running.
+#
+# The swap file name may contain "%p" that is substituted with the PID of
+# the Redis process, so the default name /tmp/redis-%p.vm will work even
+# with multiple instances as Redis will use, for example, redis-811.vm
+# for one instance and redis-593.vm for another one.
+#
+# Useless to say, the best kind of disk for a Redis swap file (that's accessed
+# at random) is a Solid State Disk (SSD).
+#
+# *** WARNING *** if you are using a shared hosting the default of putting
+# the swap file under /tmp is not secure. Create a dir with access granted
+# only to Redis user and configure Redis to create the swap file there.
+vm-swap-file /tmp/redis-%p.vm
+

 # vm-max-memory configures the VM to use at max the specified amount of
 # RAM. Everything that deos not fit will be swapped on disk *if* possible, that
 # is, if there is still enough contiguous space in the swap file.
 #
 # vm-max-memory configures the VM to use at max the specified amount of
 # RAM. Everything that deos not fit will be swapped on disk *if* possible, that
 # is, if there is still enough contiguous space in the swap file.
 #

-# With vm-max-memory 10000000 the system will swap almost everything it
-# can. Not a good default, just specify the max amount of RAM you can
-# in bytes, but it's better to leave some margin. For instance specify
-# an amount of RAM that's more or less 80% of your free RAM.
-vm-max-memory 10000000
+# With vm-max-memory 0 the system will swap everything it can. Not a good
+# default, just specify the max amount of RAM you can in bytes, but it's
+# better to leave some margin. For instance specify an amount of RAM
+# that's more or less between 60 and 80% of your free RAM.
+vm-max-memory 0

 
 # Redis swap files is split into pages. An object can be saved using multiple
 # contiguous pages, but pages can't be shared between different objects.
 
 # Redis swap files is split into pages. An object can be saved using multiple
 # contiguous pages, but pages can't be shared between different objects.


@@ -201,7 +222,7 @@ vm-max-memory 10000000
 # If you use a lot of small objects, use a page size of 64 or 32 bytes.
 # If you use a lot of big objects, use a bigger page size.
 # If unsure, use the default :)
 # If you use a lot of small objects, use a page size of 64 or 32 bytes.
 # If you use a lot of big objects, use a bigger page size.
 # If unsure, use the default :)

-vm-page-size 256
+vm-page-size 32

 
 # Number of total memory pages in the swap file.
 # Given that the page table (a bitmap of free/used pages) is taken in memory,
 
 # Number of total memory pages in the swap file.
 # Given that the page table (a bitmap of free/used pages) is taken in memory,


@@ -209,12 +230,12 @@ vm-page-size 256
 #
 # The total swap size is vm-page-size * vm-pages
 #
 #
 # The total swap size is vm-page-size * vm-pages
 #

-# With the default of 256-bytes memory pages and 104857600 pages Redis will
-# use a 25 GB swap file, that will use roughly 13 MB of RAM for the page table.
+# With the default of 32-bytes memory pages and 134217728 pages Redis will
+# use a 4 GB swap file, that will use 16 MB of RAM for the page table.

 #
 # It's better to use the smallest acceptable value for your application,
 # but the default is large in order to work in most conditions.
 #
 # It's better to use the smallest acceptable value for your application,
 # but the default is large in order to work in most conditions.

-vm-pages 104857600
+vm-pages 134217728

 
 # Max number of VM I/O threads running at the same time.
 # This threads are used to read/write data from/to swap file, since they
 
 # Max number of VM I/O threads running at the same time.
 # This threads are used to read/write data from/to swap file, since they


@@ -250,3 +271,10 @@ glueoutputbuf yes
 # your development environment so that we can test it better.
 shareobjects no
 shareobjectspoolsize 1024
 # your development environment so that we can test it better.
 shareobjects no
 shareobjectspoolsize 1024

+
+# Hashes are encoded in a special way (much more memory efficient) when they
+# have at max a given numer of elements, and the biggest element does not
+# exceed a given threshold. You can configure this limits with the following
+# configuration directives.
+hash-max-zipmap-entries 64
+hash-max-zipmap-value 512