Alexey Kukushkin created IGNITE-16431:
-----------------------------------------
Summary: Entry expiration requires twice the entry size of heap
Key: IGNITE-16431
URL: https://issues.apache.org/jira/browse/IGNITE-16431
Project: Ignite
Issue Type: Improvement
Affects Versions: 2.12
Reporter: Alexey Kukushkin
Attachments: 500MB-put-expiry-master.png
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.
!500MB-put-expiry-master.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
