Alawn/Chronicle-Map
1
0
Fork 0
mirror of https://github.com/OpenHFT/Chronicle-Map.git synced 2021-09-13 01:26:12 +00:00
Code Releases Activity

HCOLL-197 reworeded Oversized Entries Support

Browse Source
This commit is contained in:
Rob Austin
2014-12-23 09:59:44 +00:00
parent e422050102
commit 587cbd3fe1
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8 -6
View File
@@ -601,13 +601,15 @@ If after some business logic, in our example after reading the 'issueDate' and
## Oversized Entries Support
It is possible for the size of your entry to be 64 times as large as the maximum entry size,
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 larger than the others, in this case your large entry will
span across a number of entries. The alternative would be to increase your maximum entry size to be similar
It is possible for the size of your entry to be larger than the space which chronicle map
internally allocates to each 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 larger than the others, in this case your large entry will
span across a number of entries. The alternative would be to increase the internal 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.
entries are no where near the max entry size. So put simply Chronicle map is able to accept entries
where each can have a different size but it does this in a way that is not wasteful of space.
## Serialization