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

feat: Implement a configurable cache eviction policy #21

Open
helloscoopa opened this issue Sep 29, 2024 · 0 comments
Open

feat: Implement a configurable cache eviction policy #21

helloscoopa opened this issue Sep 29, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@helloscoopa
Copy link
Owner

Problem: Right now, if the cache grows too large, there's no mechanism (apart from TTL-based eviction) to automatically remove entries. Memory could be exhausted in long-running applications.

Improvement: Implement configurable cache eviction policies like Least Recently Used (LRU), Least Frequently Used (LFU), to enforce eviction. This would automatically remove older or less frequently used entries to manage memory more efficiently.

@helloscoopa helloscoopa added the enhancement New feature or request label Sep 29, 2024
@helloscoopa helloscoopa added this to the v1.5.0 milestone Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant