Details
-
Improvement
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
2.12
-
None
-
None
-
Docs Required, Release Notes Required
Description
Ignite takes twice the entry size off the heap to expire the entry when eagerTtl=true. See the attached heap memory usage diagram of putting and then expiring a 500MB entry in Ignite.
This makes Ignite inefficient with handling large objects causing OutOfMemory errors.
Do we really need loading entry's value on heap at all to expiry the entry? Please enhance Ignite cache entry expiration not to load the entry's value on heap even once or explain why it is not possible.
