You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently several classes in the framework use ConcurrentReferenceHashMap with soft references for caching. Unfortunately soft references only get cleared when the JVM is completely out of memory making it appear that Spring is consuming a lot of resources.
We could create a dedicated MemoryCache abstraction with additional bounds to ensure that no individual cache is consuming too much memory.
Another, perhaps simpler approach, could be to clear caches after the ApplicationContext has loaded. The ResolvableType cache especially could benefit from this approach.
Phil Webb opened SPR-13093 and commented
Currently several classes in the framework use
ConcurrentReferenceHashMap
with soft references for caching. Unfortunately soft references only get cleared when the JVM is completely out of memory making it appear that Spring is consuming a lot of resources.We could create a dedicated
MemoryCache
abstraction with additional bounds to ensure that no individual cache is consuming too much memory.Another, perhaps simpler approach, could be to clear caches after the
ApplicationContext
has loaded. TheResolvableType
cache especially could benefit from this approach.Affects: 4.1.6
Issue Links:
0 votes, 5 watchers
The text was updated successfully, but these errors were encountered: