From 7888702955cad9dd94ea1e471acdcf5ddd498084 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 7 Jun 2023 11:27:02 -0400 Subject: [PATCH] update --- ..._17_8fe8c0747a69ea977942a399ac929e77._comment | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/doc/bugs/importtree_spends_hours_reading_cidsdb/comment_17_8fe8c0747a69ea977942a399ac929e77._comment b/doc/bugs/importtree_spends_hours_reading_cidsdb/comment_17_8fe8c0747a69ea977942a399ac929e77._comment index 47fdb4078f..90fbd5e7a7 100644 --- a/doc/bugs/importtree_spends_hours_reading_cidsdb/comment_17_8fe8c0747a69ea977942a399ac929e77._comment +++ b/doc/bugs/importtree_spends_hours_reading_cidsdb/comment_17_8fe8c0747a69ea977942a399ac929e77._comment @@ -8,10 +8,16 @@ being checked out, is Command.Sync.updateBranches. In my repo with 10000 files, when not using --content, that is responsible for most of the run time of a sync when there is nothing new to import or pull. -It should be possible for sync to avoid running that when it didn't pull -any changes that need to be propagated back to the parent branch from the -adjusted branch. +That happens because `git-annex adjust --unlock-present` was used. So sync +needs to update the branch if there have been any changes to the content +that is present. Currently when in such an adjusted branch, it re-builds +the branch every time it's run. -With the master branch checked out instead, `git-annex sync --content` is -now as fast as `git-annex find --not --in source`. +It would be possible to avoid that when there have been no changes to the +content that is present, but it would need to deal with eg a previous sync +command having transferred some content before it was interrupted. So it +would need some kind of flag file to be written when content changes. + +(With the master branch checked out instead, `git-annex sync --content` is +now as fast as `git-annex find --not --in source`.) """]]