comment
authorJoey Hess <joeyh@joeyh.name>
Tue, 12 Jul 2022 21:00:36 +0000 (17:00 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 12 Jul 2022 21:00:36 +0000 (17:00 -0400)
doc/bugs/performance_regression__63___init_takes_times_more/comment_3_d92bd84ab3f218eb6ad38fcc7f54c223._comment [new file with mode: 0644]

diff --git a/doc/bugs/performance_regression__63___init_takes_times_more/comment_3_d92bd84ab3f218eb6ad38fcc7f54c223._comment b/doc/bugs/performance_regression__63___init_takes_times_more/comment_3_d92bd84ab3f218eb6ad38fcc7f54c223._comment
new file mode 100644 (file)
index 0000000..1e3e52d
--- /dev/null
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2022-07-12T20:51:05Z"
+ content="""
+The last time I worked on optimising this, 
+in [[todo/speed_up_keys_db_update_with_git_streaming]],
+it looked like writing to sqlite was probably a large part of the remaining
+time. Processing 100k new files took 41 seconds, and processing 100k
+removed files took only 17 seconds. And the only difference as far as what
+git-annex is doing in those cases is adding to sqlite vs removing from
+sqlite.
+
+[This comment](https://git-annex.branchable.com/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/#comment-5d4037307a3e66304cc0e8ce137e1693)
+suggests using multi-value sqlite inserts as perhaps a way to speed it up.
+Perhaps.
+"""]]