X-Git-Url: https://git.saurik.com/redis.git/blobdiff_plain/5e1d2d30f7b96c0aa808f8c6f9b267880c6097ca..92cc20ecfe195e3f08832200b1efc8911fe586f8:/tests/assets/default.conf?ds=inline diff --git a/tests/assets/default.conf b/tests/assets/default.conf index 150eb690..1b234504 100644 --- a/tests/assets/default.conf +++ b/tests/assets/default.conf @@ -291,40 +291,14 @@ appendfsync everysec # "no" that is the safest pick from the point of view of durability. no-appendfsync-on-rewrite no -#################################### 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 -# have at max a given numer of elements, and the biggest element does not +# have at max a given number 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 +hash-max-ziplist-entries 64 +hash-max-ziplist-value 512 # Similarly to hashes, small lists are also encoded in a special way in order # to save a lot of space. The special representation is only used when @@ -343,7 +317,7 @@ set-max-intset-entries 512 # order to help rehashing the main Redis hash table (the one mapping top-level # keys to values). The hash table implementation redis uses (see dict.c) # performs a lazy rehashing: the more operation you run into an hash table -# that is rhashing, the more rehashing "steps" are performed, so if the +# that is rehashing, the more rehashing "steps" are performed, so if the # server is idle the rehashing is never complete and some more memory is used # by the hash table. #