Hello, Naveen In Ignite, when we talk about rotating data between disk and memory in the data region with native persistence, we call it 'replacement', not 'eviction'. Currently, there is only one replacement policy - Random-LRU. Perhaps, there will be more policies soon, but without the ability to implement custom user policies (see IEP [1] and related ticket [2]). Replacement works on the page-level, not entry-level. It started when page memory is full and we need to load some pages from the disk. Ignite doesn't perform the premature replacement or premature page loads, page loaded and replacement occurs only on demand. It's unlikely that a custom replacement policy based on entries will be effective.
[1]: https://cwiki.apache.org/confluence/display/IGNITE/IEP-62+Page+replacement+improvements [2]: https://issues.apache.org/jira/browse/IGNITE-13761 вт, 19 янв. 2021 г. в 09:03, Naveen <[email protected]>: > Hi Stephen > > on the same mail chain, we also data like OTP (one time passwds) which are > no relevant after a while, but we dont want to expire or delete them, just > get them flushed to disk, like wise we do have other requirements where > data > is very relevant only for a certain duration, later on its not important. > Thats the whole idea of exploring eviction policies > > Naveen > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
