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.

Sign up for GitHub

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

Jump to bottom

Disable or limit caches when db-sync reaches the tip of the chain #1843

Open
kderme opened this issue Sep 3, 2024 · 1 comment · May be fixed by #1886
Open

Disable or limit caches when db-sync reaches the tip of the chain #1843

kderme opened this issue Sep 3, 2024 · 1 comment · May be fixed by #1886
Assignees
@Cmdv
Labels
enhancement New feature or request

Comments

@kderme
Copy link
Contributor

kderme commented Sep 3, 2024

Caches are used to speed up syncing. However they use memory. We could disable or reduce the caches when db-sync approaches the tip of the chain ie 30 mins before tip.
@kderme kderme added the enhancement New feature or request label Sep 3, 2024
@Cmdv Cmdv self-assigned this Oct 25, 2024
@Cmdv Cmdv linked a pull request Oct 29, 2024 that will close this issue
Draft
9 tasks
@Cmdv
Copy link
Contributor

Cmdv commented Oct 31, 2024

what to do with each cache:

cPools leave as is
cPrevBlock leave as is
cStats leave as is
cEpoch leave as is
cTxId delete and don't use again
cStake delete and don't use again
cDatum delete and don't use again
cMultiAssets delete and limit the size of LRU

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Cmdv Cmdv

Labels
enhancement New feature or request
Projects
DBSync
Status: In Progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

1843 - limit cache when close to tip IntersectMBO/cardano-db-sync
2 participants
@Cmdv @kderme