non-blocking VM data structures, just a start

1 files changed, 11 insertions, 3 deletions

diff --git a/redis.conf b/redis.conf
index ac90eb4ca..b541cbe20 100644
--- a/redis.conf
+++ b/redis.conf
@@ -101,7 +101,7 @@ dir ./
 
 # Set the max number of connected clients at the same time. By default there
 # is no limit, and it's up to the number of file descriptors the Redis process
-# is able to open. The special value '0' means no limts.
+# is able to open. The special value '0' means no limits.
 # Once the limit is reached Redis will close all the new connections sending
 # an error 'max number of clients reached'.
 #
@@ -200,7 +200,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 defualt :)
+# If unsure, use the default :)
 vm-page-size 256
 
 # Number of total memory pages in the swap file.
@@ -210,12 +210,20 @@ vm-page-size 256
 # 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 rougly 13 MB of RAM for the page table.
+# use a 25 GB swap file, that will use roughly 13 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.
 vm-pages 104857600
 
+# 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
+# also encode and decode objects from disk to memory or the reverse, a bigger
+# number of threads can help with big objects even if they can't help with
+# I/O itself as the physical device may not be able to couple with many
+# reads/writes operations at the same time.
+vm-max-threads 4
+
 ############################### ADVANCED CONFIG ###############################
 
 # Glue small output buffers together in order to send small replies in a