diff --git a/doc/bugs/performance_regression__63___init_takes_times_more/comment_1_3f32fa3c6de412bfdab8a4e67a30012c._comment b/doc/bugs/performance_regression__63___init_takes_times_more/comment_1_3f32fa3c6de412bfdab8a4e67a30012c._comment
new file mode 100644
index 0000000000..6cbf062cd8
--- /dev/null
+++ b/doc/bugs/performance_regression__63___init_takes_times_more/comment_1_3f32fa3c6de412bfdab8a4e67a30012c._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-07-12T20:34:02Z"
+ content="""
+Notice that it says "scanning for annexed files", not "unlocked files"
+anymore.
+
+The reason it's slower is explained by [[!commit 428c91606b]].
+And that was necessary to fix the bad, longstanding bug
+[[bugs/indeterminite_preferred_content_state_for_duplicated_file]].
+It has to scan every annexed file, not only the unlocked ones,
+in order to collect the data to not have that bug.
+
+And the scan got optimised as well as possible, I think, at the time,
+see the old issue you filed @yoh, 
+<https://git-annex.branchable.com/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/>
+"""]]
diff --git a/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_19_b34a9cf4114ed943fe4ba2de78eb0bbc._comment b/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_19_b34a9cf4114ed943fe4ba2de78eb0bbc._comment
index 2f68e41293..b7bacf2f90 100644
--- a/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_19_b34a9cf4114ed943fe4ba2de78eb0bbc._comment
+++ b/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_19_b34a9cf4114ed943fe4ba2de78eb0bbc._comment
@@ -16,4 +16,4 @@ it might need to update a pointer file. Eg, when `git annex get` is run.
 Avoiding using the keys db when annex.supportunlocked=false in all such
 cases in order to avoid the scan would be effectively the same complexity
 as continuing to support v5 repos, which I've NAKed before.
-""]]
+"""]]