From 60ad0c2ce9425a15b14fa671a307741b6b150459 Mon Sep 17 00:00:00 2001 From: boundedbuffer Date: Sun, 7 Dec 2014 21:59:12 +0000 Subject: [PATCH] updated Entry size --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a7a2a24bc..9bb5765a4 100644 --- a/README.md +++ b/README.md @@ -328,7 +328,7 @@ mapping, ( calculated as 4GB = 2^20 * 4 KB pages). Windows doesn't fail when a m Chronicle Map allocates head room which is a waste on Windows (Linux's sparse allocation means the head room has little impact). -For production systems +##### For production - on Windows we recommend you use map sizes of less than 4 GB each, and less than 50% main memory in total. - on Linux we recommend you use small to large maps of less than double main memory. e.g. if you have a 128 GB server, we recommend you have less than 256 GB of maps on the server. - on Mac OSX, we have no specific recommendations.