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

The "hot" data should be loaded into memory instead of being repeatedly loaded from disk to reduce latencies and let IOPS to be used for writes, reading uncacheble data (e.g. way too big keys) or reading new data #132

Open
danielealbano opened this issue Jul 3, 2022 · 0 comments
Open

The "hot" data should be loaded into memory instead of being repeatedly loaded from disk to reduce latencies and let IOPS to be used for writes, reading uncacheble data (e.g. way too big keys) or reading new data #132

danielealbano opened this issue Jul 3, 2022 · 0 comments
Labels
enhancement New feature or request
Projects
cachegrand
Milestone
v0.5

Comments

@danielealbano
Copy link
Owner

No description provided.

@danielealbano danielealbano created this issue from a note in cachegrand (Ready for Work) Jul 3, 2022
@danielealbano danielealbano added the enhancement New feature or request label Jul 3, 2022
@danielealbano danielealbano added this to the v0.4 milestone Jul 3, 2022
@danielealbano danielealbano modified the milestones: v0.4, v0.5 May 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
cachegrand
  
Ready for Work
Milestone
v0.5
Development

No branches or pull requests
1 participant
@danielealbano