diff options
| author | antirez <antirez@gmail.com> | 2011-06-25 12:22:03 +0200 |
|---|---|---|
| committer | antirez <antirez@gmail.com> | 2011-06-25 12:22:03 +0200 |
| commit | c9d0c3623a7714bd41a35237f4ba927206a7adb6 (patch) | |
| tree | 691c04cd364b578f5043ca2bc089a5d333bc737e /tests/assets | |
| parent | c1c9d551da6dd534c8dae051a3a7e64bf7db6bfb (diff) | |
| download | redis-c9d0c3623a7714bd41a35237f4ba927206a7adb6.tar.gz | |
diskstore removed
Diffstat (limited to 'tests/assets')
| -rw-r--r-- | tests/assets/default.conf | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/tests/assets/default.conf b/tests/assets/default.conf index 150eb6907..75334426b 100644 --- a/tests/assets/default.conf +++ b/tests/assets/default.conf @@ -291,32 +291,6 @@ 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 |