From a40f70b388bfe41d902503f5575ffa06afaf95ca Mon Sep 17 00:00:00 2001 From: tomdhunt Date: Tue, 5 Oct 2021 22:07:45 +0000 Subject: [PATCH] Added a comment --- ...comment_8_c5e3d0c826de72eb0ca9dff51104a0ab._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/borg_special_remote_memory_usage_high_for_large_borg_repo/comment_8_c5e3d0c826de72eb0ca9dff51104a0ab._comment diff --git a/doc/bugs/borg_special_remote_memory_usage_high_for_large_borg_repo/comment_8_c5e3d0c826de72eb0ca9dff51104a0ab._comment b/doc/bugs/borg_special_remote_memory_usage_high_for_large_borg_repo/comment_8_c5e3d0c826de72eb0ca9dff51104a0ab._comment new file mode 100644 index 0000000000..a8a2134f8f --- /dev/null +++ b/doc/bugs/borg_special_remote_memory_usage_high_for_large_borg_repo/comment_8_c5e3d0c826de72eb0ca9dff51104a0ab._comment @@ -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.) +"""]]