mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2021-10-05 20:28:26 -04:00
commit 68b4fc6018
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/bugs/borg_special_remote_memory_usage_high_for_large_borg_repo/comment_7_2316ba67144849988632c79e5a59a3f6._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="tomdhunt"
avatar="http://cdn.libravatar.org/avatar/02694633d0fb05bb89f025cf779218a3"
subject="comment 7"
date="2021-10-05T21:30:03Z"
content="""
Yeah, I'm not familiar with the internal architecture but both borg and git-annex handle this dataset fine on their own, so it seems that the intersection between the two should also be doable.
"""]]

10
doc/bugs/borg_special_remote_memory_usage_high_for_large_borg_repo/comment_8_c5e3d0c826de72eb0ca9dff51104a0ab._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="tomdhunt"
avatar="http://cdn.libravatar.org/avatar/02694633d0fb05bb89f025cf779218a3"
subject="comment 8"
date="2021-10-05T22:07:44Z"
content="""
If it's just a matter of storing the whole set of keys present in each individual archive, you might be able to handle it via difference encoding. The whole list for the first archive, then just sets of added/removed for each archive after that.
This adds a runtime cost to getting the whole set for any archive after the first one, but even with a few thousand archives it seems that should be relatively small. (I assume that it's more likely to have huge numbers of items in an archive, than huge numbers of archives in a repository.)
"""]]