From 7dc977bd292463a871d0fb56cb5ff7e7ee78b684 Mon Sep 17 00:00:00 2001 From: Rob Austin Date: Wed, 6 May 2015 16:40:08 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 43e97ca00..0818f0ccd 100644 --- a/README.md +++ b/README.md @@ -318,7 +318,7 @@ ChronicleMap is able to map memory to a file and hence this can impact the total able to configure. - Windows allocates memory and disk eagerly. Windows will fail if more than 4 GB is allocated in a single memory -mapping, ( calculated as 4GB = 2^20 * 4 KB pages). Windows doesn't fail when a memory mapped region is mapped, rather it will fail when it is used up. This limitation doesn't apply to newer or server based versions of Windows. Eager memory allocation means you can't map more than free memory, but it should reduce jitter when you use it. In the future we may support multiple mappings to avoid this limitation, but there is no immediate plan to do so. +mapping, ( calculated as 4GB = 2^20 * 4 KB pages). Windows doesn't fail when a memory mapped region is mapped, rather it will fail when it is used up. Eager memory allocation means you can't map more than free memory, but it should reduce jitter when you use it. In the future we may support multiple mappings to avoid this limitation, but there is no immediate plan to do so. - Linux allocates memory and disk lazily. Linux systems see a performance degradation at around 200% of main memory. - Mac OSX allocates memory lazily and disk eagerly.