From 3a53e89dbcf9f6921c975f2d6e8de1193385482a Mon Sep 17 00:00:00 2001 From: Josh Baker Date: Tue, 26 Jul 2016 10:28:03 -0700 Subject: [PATCH] updated shrink value --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4d66f23..ea77070 100644 --- a/README.md +++ b/README.md @@ -345,7 +345,7 @@ When the database opens again, it will read back the aof file and process each c As you may guess this log file can grow large over time. There is a `Shrink()` function which will rewrite the aof file so that it contains only the items in the database. The shrink operation does not lock up the database so read and write transactions can continue while shrinking is in process. -Also there's the database config setting `Config.AutoShrink` which is used to allow for shrinking to be self-managed. This value is set to a multiple that represents how many more entries in the aof file versus the number of items in memory. For example; If this value is set to 10 and the number of item in memory is 150,000, then the database will automatically shrink when the aof file has 1,500,000 lines in it. Currently default value is 5, but this may change in a future release. Autoshink can be disabled by setting this value to zero. +Also there's the database config setting `Config.AutoShrink` which is used to allow for shrinking to be self-managed. This value is set to a multiple that represents how many more entries in the aof file versus the number of items in memory. For example; If this value is set to 10 and the number of item in memory is 150,000, then the database will automatically shrink when the aof file has 1,500,000 lines in it. Currently default value is 50, but this may change in a future release. Autoshink can be disabled by setting this value to zero. ### Durability and fsync