From 53a2a35a0d6221c25e9f992ef3c0464229e4a894 Mon Sep 17 00:00:00 2001 From: Enrico Giordani Date: Wed, 16 Dec 2015 15:14:34 +0100 Subject: [PATCH] [Docs] Added info about the memory working set showed by the task manager. --- msvs/setups/documentation/redis.windows-service.conf | 12 ++++++++++++ msvs/setups/documentation/redis.windows.conf | 12 ++++++++++++ 2 files changed, 24 insertions(+) diff --git a/msvs/setups/documentation/redis.windows-service.conf b/msvs/setups/documentation/redis.windows-service.conf index ba7992e6..aa041067 100644 --- a/msvs/setups/documentation/redis.windows-service.conf +++ b/msvs/setups/documentation/redis.windows-service.conf @@ -453,6 +453,18 @@ slave-priority 100 # WARNING: not setting maxmemory will cause Redis to terminate with an # out-of-memory exception if the heap limit is reached. # +# NOTE: since Redis uses the system paging file to allocate the heap memory, +# the Working Set memory usage showed by the Windows Task Manager or by other +# tools such as ProcessExplorer will not always be accurate. For example, right +# after a background save of the RDB or the AOF files, the working set value +# may drop significantly. In order to check the correct amount of memory used +# by the redis-server to store the data, use the INFO client command. The INFO +# command shows only the memory used to store the redis data, not the extra +# memory used by the Windows process for its own requirements. Th3 extra amount +# of memory not reported by the INFO command can be calculated subtracting the +# Peak Working Set reported by the Windows Task Manager and the used_memory_peak +# reported by the INFO command. +# # maxmemory # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory diff --git a/msvs/setups/documentation/redis.windows.conf b/msvs/setups/documentation/redis.windows.conf index 7a0ea37a..6e5880eb 100644 --- a/msvs/setups/documentation/redis.windows.conf +++ b/msvs/setups/documentation/redis.windows.conf @@ -453,6 +453,18 @@ slave-priority 100 # WARNING: not setting maxmemory will cause Redis to terminate with an # out-of-memory exception if the heap limit is reached. # +# NOTE: since Redis uses the system paging file to allocate the heap memory, +# the Working Set memory usage showed by the Windows Task Manager or by other +# tools such as ProcessExplorer will not always be accurate. For example, right +# after a background save of the RDB or the AOF files, the working set value +# may drop significantly. In order to check the correct amount of memory used +# by the redis-server to store the data, use the INFO client command. The INFO +# command shows only the memory used to store the redis data, not the extra +# memory used by the Windows process for its own requirements. Th3 extra amount +# of memory not reported by the INFO command can be calculated subtracting the +# Peak Working Set reported by the Windows Task Manager and the used_memory_peak +# reported by the INFO command. +# # maxmemory # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory -- GitLab