[
https://issues.apache.org/jira/browse/COLLECTIONS-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030249#comment-15030249
]
Thomas Neidhart commented on COLLECTIONS-557:
---------------------------------------------
Fix version is set to 4.1 and this improvement is not in the 3.2.2 release as
this was bugfix only.
> LRUMap memory usage vs size
> ---------------------------
>
> Key: COLLECTIONS-557
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-557
> Project: Commons Collections
> Issue Type: Improvement
> Components: Map
> Affects Versions: 3.2.1
> Reporter: Philippe Mouawad
> Labels: MEMORY
> Fix For: 4.1
>
>
> Hello,
> Currently LRUMap uses maxSize parameter to configure its maxSize.
> This is not great for its memory usage.
> For example I have a use case where I can't really guess the target maxSize
> of LRUMap so I have put a big number .
> In reality I end up having 380 elements but LRUMap uses 33 Mb of memory
> because it allocates (as capacity) LOAD_FACTORxsupposed max size.
> It would be nice to have the possibility to set maxSize apart making it
> unrelated to capacity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
