Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Framework Core
-
Labels:None
Description
To make Ehcache caching more memory-friendly, consider wrapping the Element}}s we store in the cache with {{SoftReference}}s, which would enable the garbage collector to reclaim cached memory if needed. One strategy for making this work with the {{SelfPopulatingCache we use would be to test the contents of the SoftReference on each get and if the contents is empty, removing the element from the cache and requesting it again, which should create a new one through the SelfPopulatingCache's factory.
Issue Links
| This issue is related to: | ||||
| CARROT-571 | Processing results cache takes up too much memory |
|
|
|
3.2.0 release will concentrate on processing language infrastructure, bug fixes and build script improvements.