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

L2s should follow the cache on second miss rule and hydrate their persistent cache asynchronously from IPFS Gateway #6

Open
aarshkshah1992 opened this issue May 25, 2022 · 0 comments
Open

L2s should follow the cache on second miss rule and hydrate their persistent cache asynchronously from IPFS Gateway #6

aarshkshah1992 opened this issue May 25, 2022 · 0 comments
Assignees
@aarshkshah1992
Labels
L2 Requires work on the L2 node persistent-caching
Milestone
M0.5

Comments

@aarshkshah1992
Copy link
Contributor

aarshkshah1992 commented May 25, 2022 •
edited
Loading

See the Cache-on-second-hit rule section in Section 4.2 of this Akamai paper.

Most content is only ever requested once(~75% as per the paper). If some content is popular, it will be accessed atleast twice and persisting only such content in the cache improves the cache hit ratio and reduces disk IO/cache-churn on the nodes.

Once an L2 decides to persist some content in it's cache, the L2 should escape to the IPFS Gateway and cache it.
@aarshkshah1992 aarshkshah1992 added L2 Requires work on the L2 node persistent-caching labels May 25, 2022
@aarshkshah1992 aarshkshah1992 self-assigned this May 25, 2022
@aarshkshah1992 aarshkshah1992 mentioned this issue May 25, 2022
Open
@aarshkshah1992 aarshkshah1992 changed the title L2s should hydrate their persistent cache asynchronously from IPFS Gateway L2s should follow the cache on second miss rule and hydrate their persistent cache asynchronously from IPFS Gateway Jun 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@aarshkshah1992 aarshkshah1992

Labels
L2 Requires work on the L2 node persistent-caching
Projects
None yet
Milestone
M0.5
Development

No branches or pull requests
1 participant
@aarshkshah1992