[jira] [Updated] (IGNITE-16431) Entry expiration requires twice the entry size of heap

["Alexey Kukushkin (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-16431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kukushkin updated IGNITE-16431:
--------------------------------------
    Remaining Estimate: 168h
     Original Estimate: 168h

> 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
>            Priority: Major
>              Labels: cggg
>         Attachments: 500MB-put-expiry-master.png
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> 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.7#820007)