Skip to content
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.

L1 and L2 nodes evict persisted cache content according to an LRU policy #4

Open
aarshkshah1992 opened this issue May 25, 2022 · 2 comments
Assignees
Labels
L2 Requires work on the L2 node persistent-caching
Milestone

Comments

@aarshkshah1992
Copy link
Contributor

aarshkshah1992 commented May 25, 2022

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.

@aarshkshah1992 aarshkshah1992 added L2 Requires work on the L2 node L1 Requires work on the L1 node labels May 25, 2022
@aarshkshah1992 aarshkshah1992 self-assigned this May 25, 2022
@DiegoRBaquero
Copy link

This is already the case for L1s as it's nginx cache implementation.

@aarshkshah1992 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
@aarshkshah1992 aarshkshah1992 added L2 Requires work on the L2 node and removed L2 Requires work on the L2 node L1 Requires work on the L1 node labels May 30, 2022
@aarshkshah1992
Copy link
Contributor Author

@DiegoRBaquero Have edited the issue to do this for L2s only.

@aarshkshah1992 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 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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
L2 Requires work on the L2 node persistent-caching
Projects
None yet
Development

No branches or pull requests

2 participants