Is there Ignite Eviction low water mark

classic Classic list List threaded Threaded
3 messages Options
HEWA WIDANA GAMAGE, SUBASH HEWA WIDANA GAMAGE, SUBASH
Reply | Threaded
Open this post in threaded view
|

Is there Ignite Eviction low water mark

Hi all,

This is to understand how eviction works in Ignite cache.

 

For example, let’s say the LRU eviction policy is set to max 100MB. Then, when the cache size reached 100MB, how much of LRU entries will get evicted ? Is there any low water mark/percentage ? Like eviction policy will remove 20% of the cache, and then let it again reach back to 100MB to clean up again.

 

Also please confirm whether the behavior is same in Ignite 1.9 vs 2.6.

Denis Mekhanikov Denis Mekhanikov
Reply | Threaded
Open this post in threaded view
|

Re: Is there Ignite Eviction low water mark

Hi!

Ignite 2.x has a mechanism called page eviction. It's configured using DataRegion#pageEvictionMode.
Page eviction removes entries from a data region until either DataRegionConfiguration#evictionThreshold is reached,
or DataRegionConfiguration#emptyPagesPoolSize pages are available in the free list.
It's applied only when persistence is disabled. Otherwise data is just spilled to disk.

Ignite 1.x has a different kind of eviction, since it doesn't have page memory nor data regions.
It removes data until occupied memory is bellow LruEvictionPolisy#maxSize.
This is similar to on-heap eviction policy in Ignite 2.x, but you don't need to use it
unless you know exactly what you're doing and what an on-heap cache is.

Denis

пт, 2 нояб. 2018 г. в 21:35, HEWA WIDANA GAMAGE, SUBASH <[hidden email]>:

Hi all,

This is to understand how eviction works in Ignite cache.

 

For example, let’s say the LRU eviction policy is set to max 100MB. Then, when the cache size reached 100MB, how much of LRU entries will get evicted ? Is there any low water mark/percentage ? Like eviction policy will remove 20% of the cache, and then let it again reach back to 100MB to clean up again.

 

Also please confirm whether the behavior is same in Ignite 1.9 vs 2.6.

HEWA WIDANA GAMAGE, SUBASH HEWA WIDANA GAMAGE, SUBASH
Reply | Threaded
Open this post in threaded view
|

RE: Is there Ignite Eviction low water mark

In Ignite 1.x vs 2.x, when we get notified about an eviction (from cache events),  will Ignite literally delete the entry, or can they be remain  for certain period and later get wiped out.

 

The implementation of eviction from 1.x to 2.x is a different, new one?

 

 

From: Denis Mekhanikov [mailto:[hidden email]]
Sent: Monday, November 05, 2018 7:22 AM
To: user
Subject: Re: Is there Ignite Eviction low water mark

 

This email is from an external source - exercise caution regarding links and attachments.

Hi!

 

Ignite 2.x has a mechanism called page eviction. It's configured using DataRegion#pageEvictionMode.

Page eviction removes entries from a data region until either DataRegionConfiguration#evictionThreshold is reached,

or DataRegionConfiguration#emptyPagesPoolSize pages are available in the free list.

It's applied only when persistence is disabled. Otherwise data is just spilled to disk.

 

Ignite 1.x has a different kind of eviction, since it doesn't have page memory nor data regions.

It removes data until occupied memory is bellow LruEvictionPolisy#maxSize.

This is similar to on-heap eviction policy in Ignite 2.x, but you don't need to use it

unless you know exactly what you're doing and what an on-heap cache is.

 

Denis

 

пт, 2 нояб. 2018 г. в 21:35, HEWA WIDANA GAMAGE, SUBASH <[hidden email]>:

Hi all,

This is to understand how eviction works in Ignite cache.

 

For example, let’s say the LRU eviction policy is set to max 100MB. Then, when the cache size reached 100MB, how much of LRU entries will get evicted ? Is there any low water mark/percentage ? Like eviction policy will remove 20% of the cache, and then let it again reach back to 100MB to clean up again.

 

Also please confirm whether the behavior is same in Ignite 1.9 vs 2.6.