Why ehcache 3 does not support "Cache Eviction Algorithms"?

[moshe....@gmail.com]

Hi,

I have noticed that ehcache 3 does no longer have support for eviction algorithms / policies like LRU, LFU, etc.

I understand that there is a Eviction Advisor that can offer some capabilities but from what I understand it cannot be used to implement LRU / LFU / ... policies.


Is my understanding correct?
If so, why did ehcache 3 dropped the support for these very useful feature?
Is there any way to achieve that behavior in ehcache 3?

Thanks.

[Louis Jacomet]

Hi,

Thanks for your interest in Ehcache.

I would recommend using the ehcache-users google group for that kind of questions.

Now, the reason we dropped this is that it mostly does not scale when you want to allow configurability. And Ehcache 2.x depending on the tiering configuration was effectively ignoring that.

Could you explain why you need a strict eviction algorithm?

Regards,

Louis

--
You received this message because you are subscribed to the Google Groups "ehcache-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ehcache-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ehcache-dev/14a1d210-39b3-4dce-8754-ee31a15e361d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[moshe....@gmail.com]

Hi,

Thanks for answering. I will use ehcache-users next time. I simply thought this is a question for the developers.

My usage of the cache is usually in peaks - once an entry has entered the cache it is most likely to be used many times in the next few minutes.

My cache is limited to 10MB.

So if I have 10 requests at about the same time (each one takes 1MB) - I would like them to fill the cache replacing any other older entries (LRU).

I wouldn't like that my 2nd, 3rd, Nth request will remove an entry that was recently added.