You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Thomas Neidhart (JIRA)" <ji...@apache.org> on 2015/06/01 12:13:18 UTC
[jira] [Resolved] (COLLECTIONS-557) LRUMap memory usage vs size
[ https://issues.apache.org/jira/browse/COLLECTIONS-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Neidhart resolved COLLECTIONS-557.
-----------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.2.2)
Added support for collections 4 in r1682859.
Thanks for the report!
> 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)