Skip to content

implement an optional cache#168

Open
ThomasWaldmann wants to merge 16 commits into
borgbackup:masterfrom
ThomasWaldmann:cache
Open

implement an optional cache#168
ThomasWaldmann wants to merge 16 commits into
borgbackup:masterfrom
ThomasWaldmann:cache

Conversation

@ThomasWaldmann
Copy link
Copy Markdown
Member

No description provided.

if, as usual, there is only one level in the list,
we do not need to search for an existing item at
misc. levels - we know where it must be.
find() is usually a pure local computation (single-level fast path).
@ThomasWaldmann
Copy link
Copy Markdown
Member Author

ThomasWaldmann commented May 26, 2026

@mr-raj12 Check these changes.

Guess for borgbackup this means:

  • we do not need to implement clientside caching of repository contents there
  • to avoid confusion, we should not have a "cache" namespace in primary backend
  • just configure the Store appropriately with a caching backend
  • set cache policies for how we use the misc. namespaces (only cache content-addressed items)
  • "mirror" could be useful in future for people wanting to have a local and a remote repo that is kept in sync. the cache is the local mirror then (then it needs to be unlimited, no max_age, no size limit)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant