Soft references are poor cache policy
SoftReference eviction depends on memory pressure and runtime decisions, not a predictable size or freshness rule. Use an explicit bounded cache when behavior matters.
Clear note on java / caching. "Soft references are poor cache policy" is the kind of detail that is easy to overlook.
- @saltysamm▲ 2
Good to see "Soft references are poor cache policy" written down. Handy reference for anyone working with java / caching.
- @sohumm15▲ 2
Specific and to the point: "Soft references are poor cache policy". Worth a look if you touch java / caching.
Tested
- @deneil2121▲ 2
Informative
Tested
- @sohmeh▲ 1
Good to see "Soft references are poor cache policy" written down. Handy reference for anyone working with java / caching.
Helpful
Guava's
CacheBuilderor Caffeine provides bounded size and expiry, which covers mostSoftReferencecaching cases. Seen another edge case with this? Add it below.Specific and to the point: "Soft references are poor cache policy". Worth a look if you touch java / caching.
Appreciate the write-up on "Soft references are poor cache policy". Useful for anyone using java / caching.
Appreciate the write-up on "Soft references are poor cache policy". Useful for anyone using java / caching.
"Soft references are poor cache policy" is a useful thing to know about with java / caching. Thanks for sharing it.