From 51319f85589f8ea19747cc5f45e9009079aeac1d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 30 May 2023 17:19:23 -0400 Subject: [PATCH] update --- doc/todo/speed_up_import_tree.mdwn | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/todo/speed_up_import_tree.mdwn b/doc/todo/speed_up_import_tree.mdwn index 1e1ca45624..c9da243d1a 100644 --- a/doc/todo/speed_up_import_tree.mdwn +++ b/doc/todo/speed_up_import_tree.mdwn @@ -27,6 +27,14 @@ likely overall..) How fast can a git tree of say, 10000 files be generated? Is it faster than querying sqlite 10000 times? +Once it knows which files are changed, it still needs to generate the +imported tree, which contains both changed and unchanged files. How to +handle unchanged files when generating that tree? Current method is +to do a database lookup to convert the ContentIdentifier into a Key, and +record that in the tree. But those database lookups are the slow thing that +needs to be avoided. Seems like it will need to either use adjustTree, or a +separate index file. (The index file would make importing a History hard.) + ---- Another idea would to be use something faster than sqlite to record the cid