[ https://issues.apache.org/jira/browse/IGNITE-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869822#comment-15869822 ]
Alexey Goncharuk commented on IGNITE-4534: ------------------------------------------ Alexey, In Ignite 1.x architecture there were 3 major areas where entries could be stored: on-heap, off-heap and swap. In Ignite 2.0 we are moving towards choosing off-heap as the primary storage and keeping some of the hot entries on-heap. However, in both Ignite 1.x and Ignite 2.x, using eviction implies that either a user can easily reconstruct evicted entries on-the-fly, or there is a backing write-through cache store keeping cache entries. Otherwise, eviction can effectively remove data from the cache. > Implement offheap eviction policies based on page memory > -------------------------------------------------------- > > Key: IGNITE-4534 > URL: https://issues.apache.org/jira/browse/IGNITE-4534 > Project: Ignite > Issue Type: Sub-task > Components: cache > Reporter: Alexey Goncharuk > Assignee: Ivan Rakov > Fix For: 2.0 > > > Since the internal structure of offheap storage has changed, we need to > re-implement Fifo, Lru and Sorted eviction policies -- This message was sent by Atlassian JIRA (v6.3.15#6346)