On 02/12/2018 04:25 PM, Ivan Larionov wrote:
> On Fri, Feb 9, 2018 at 7:50 PM, Alex Rousskov wrote:
>
> please note that rock
> cache_dirs do not support/have/use a configurable replacement policy:
> Each incoming object is assigned a slot based on its key hash. With
> modern rock
On Fri, Feb 9, 2018 at 7:50 PM, Alex Rousskov <
rouss...@measurement-factory.com> wrote:
>
> I cannot answer your question for aufs, but please note that rock
> cache_dirs do not support/have/use a configurable replacement policy:
> Each incoming object is assigned a slot based on its key hash. Wi
On 02/09/2018 06:42 PM, Ivan Larionov wrote:
> Hello!
>
> Is it possible to get a metric similar to "LRU reference age" (or "LRU
> expiration") when using heap LRU/LFUDA and aufs/rock?
>
> What we need to do is to figure out the age of the oldest least accessed
> object in the cache. Or the age o
Hello!
Is it possible to get a metric similar to "LRU reference age" (or "LRU
expiration") when using heap LRU/LFUDA and aufs/rock?
What we need to do is to figure out the age of the oldest least accessed
object in the cache. Or the age of the last replaced object.
If my description is somehow u
