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

Cache pruning #438

Closed
hadley opened this issue Apr 26, 2021 · 1 comment
Closed

Cache pruning #438

hadley opened this issue Apr 26, 2021 · 1 comment

Comments

@hadley
Copy link
Member

hadley commented Apr 26, 2021

Boards should provide some default cache eviction policy, probably define maximum size and then after each cache write, automatically remove least recently used cache. Use same strategy as cachem — touch data.txt on read. Might need to enforce both maximum size and maximum number of versions.

@hadley hadley closed this as completed in 558de0c May 20, 2021
@github-actions
Copy link

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.

@github-actions github-actions bot locked and limited conversation to collaborators Aug 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant