From d78b55dbbec565ec0ef5bdcd111d398f813f3c82 Mon Sep 17 00:00:00 2001 From: Rob Austin Date: Mon, 8 Sep 2014 16:17:07 +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 699439731..6fa162bef 100644 --- a/README.md +++ b/README.md @@ -242,7 +242,7 @@ Exactly like map.getUsing(), acquireUsing() will give you back a reference to an ## Oversized Entries Support -It is possible for an entry to be twice as large as the maximum entry, we refer to this type of entry as an oversized entry. Oversized entries are there to cater for the case where only a small percentage of your entries ( say 1% ) are twise as large as the others, in this case your large entry will span across two entries. The alternative would be to increase your maximum entry size to be similar to the size of the largest entry, but this approach is wasteful of memory, especially when most entries are no where near the max entry size. +It is possible for an entry to be twice as large as the maximum entry, we refer to this type of entry as an oversized entry. Oversized entries are there to cater for the case where only a small percentage of your entries are twise as large as the others, in this case your large entry will span across two entries. The alternative would be to increase your maximum entry size to be similar to the size of the largest entry, but this approach is wasteful of memory, especially when most entries are no where near the max entry size. ## Serialization