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

Support incremental update of outdated local cache #287

Open
Nikratio opened this issue Apr 16, 2023 · 0 comments
Open

Support incremental update of outdated local cache #287

Nikratio opened this issue Apr 16, 2023 · 0 comments
Assignees

Comments

@Nikratio
Copy link
Collaborator

Currently, if the locally cached metadata is outdated, the entire database is downloaded from the backend.

We could make this a lot faster by storing the MD5 of each metadata object as object-metadata, and then only downloading objects whose MD5 differs from that of the locally cached block. For this, we probably want to implement a highly-parallel get_metadata(prefix) method for backend classes that uses multiple connections (multiplexed through async IO) to retrieve metadata for multiple objects.

The question is just: is it worth the complexity? How often do people have a partially outdated local cache.

@Nikratio Nikratio self-assigned this Apr 16, 2023
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

1 participant