From 4547a467b12ae4059a3292aa1ecce4b8f184f7b2 Mon Sep 17 00:00:00 2001 From: jgoerzen Date: Tue, 30 May 2023 00:37:10 +0000 Subject: [PATCH] --- doc/bugs/importtree_spends_hours_reading_cidsdb.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/bugs/importtree_spends_hours_reading_cidsdb.mdwn b/doc/bugs/importtree_spends_hours_reading_cidsdb.mdwn index f947d2420d..075f0c52d0 100644 --- a/doc/bugs/importtree_spends_hours_reading_cidsdb.mdwn +++ b/doc/bugs/importtree_spends_hours_reading_cidsdb.mdwn @@ -37,6 +37,8 @@ It is that last sync that runs into this problem. There are about 150,000 files in that tree. This problem occurs *after* git-annex is done scanning the tree (verified with strace and lsof). This problem does not occur with the same number of files in a local/standard git-annex repo (as opposed to the directory special remote). +.git/annex/cidsdb/db is only 51M so it is certainly entirely cached. git-annex is entirely CPU-bound at this point. + ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) Yes, and I hope to use it for a project to archive family photos and videos to BD-R (that's what this is about here)