Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine correct cache data lifecycle rules #220

Open
JesseTheRobot opened this issue Feb 15, 2025 · 1 comment
Open

Determine correct cache data lifecycle rules #220

JesseTheRobot opened this issue Feb 15, 2025 · 1 comment

Comments

@JesseTheRobot
Copy link
Member

JesseTheRobot commented Feb 15, 2025

Tracking issue

@JesseTheRobot JesseTheRobot changed the title Determine correct data lifecycle rules Determine correct cache data lifecycle rules Feb 15, 2025
@JesseTheRobot
Copy link
Member Author

Current approach is as follows:

  • Unpacked chunks shared an "ingress" cache, which is a two-tier (data_root and chunk) block-height based tagged LRU (data expires based on height the corresponding data root was last seen in a Tx, with some leeway for chunk gossip caching)
  • PD chunks use a distinct single tier (chunks only) data cache, with logic that performs expiry based on the mempool state (if the corresponding consumer txs have been processed & no new consumer Txs have been added)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant