You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.
This is already the case for L1s as it's nginx cache implementation.
aarshkshah1992
changed the title
L1 and L2 nodes evict persisted cache content according to an LRU policy
L1 nodes evict persisted cache content according to an LRU policy
May 30, 2022
@DiegoRBaquero Have edited the issue to do this for L2s only.
aarshkshah1992
changed the title
L1 nodes evict persisted cache content according to an LRU policy
L2 nodes evict persisted cache content according to an LRU policy
May 30, 2022
aarshkshah1992
changed the title
L2 nodes evict persisted cache content according to an LRU policy
L1 and L2 nodes evict persisted cache content according to an LRU policy
Jun 20, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Once the size of the persistent cache on L2s exceed a certain pre-configured threshold, we should evict entires using an LRU policy.
See Section 4 of this paper for a neat way of doing this.
The text was updated successfully, but these errors were encountered: