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

Allow cache entries to be prioritized #155

Open
Tracked by #155
frasercl opened this issue Oct 26, 2023 · 1 comment
Open
Tracked by #155

Allow cache entries to be prioritized #155

frasercl opened this issue Oct 26, 2023 · 1 comment
Assignees

Comments

@frasercl
Copy link
Collaborator

Use Case

If prefetched zarr chunks are inserted at the beginning of VolumeCache's LRU queue, they may be evicted after data that has actually been (or is being) used. This could cause all sorts of (mildly) undesirable effects.

Solution

Allow cache entries to be inserted with lower priority if they are the result of a prefetch. Resolve #152 before beginning work on this.

@frasercl
Copy link
Collaborator Author

The problem here, more specifically: when data is loaded, the actual data required for display is fetched first, then we begin prefetching outward in time/space (T-1, T+1, T-2, T+2, etc.). The new data also gets inserted into the cache in this order... making it look as though deep prefetched data is most recently used and highest priority!

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

No branches or pull requests

2 participants