From 4d581ad6b47213b30af8be2e0720b73784239f29 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Mon, 7 Jun 2021 16:11:01 +0000 Subject: [PATCH] Added a comment: deferring the keys-to-files scan --- ...nt_18_4e1e8fd89ea9be43d89e72562236c979._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_18_4e1e8fd89ea9be43d89e72562236c979._comment diff --git a/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_18_4e1e8fd89ea9be43d89e72562236c979._comment b/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_18_4e1e8fd89ea9be43d89e72562236c979._comment new file mode 100644 index 0000000000..6927ab0085 --- /dev/null +++ b/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_18_4e1e8fd89ea9be43d89e72562236c979._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="deferring the keys-to-files scan" + date="2021-06-07T16:11:00Z" + content=""" +>The scan could be done lazily, but there are situations that use the database where unexpectedly taking a much longer time than usual would be a real problem + +For unlocked files, certainly. When `annex.supportunlocked=false`, it sounded like the only situation that uses the database is `drop --auto`, or a [[matching expression|git-annex-matching-options]] with `--includesamecontent/--excludesamecontent`? (And maybe [[todo/git-annex_whereused]]). +Personally I would prefer an unexpected delay in these rare cases, to a [delay](https://git-annex.branchable.com/bugs/significant_performance_regression_impacting_data!) in the more common case of checking out or switching branches. + + + +"""]] -- 2.30.2