summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawk6QAwUsFHpr3Km1yQbg8hf3S7RDYf7hX4 <Lauri@web>2012-01-27 08:12:48 +0000
committerGravatar admin <admin@branchable.com>2012-01-27 08:12:48 +0000
commitba6f01b137498b7df2191f050158f58052311624 (patch)
tree8fac3f8cbd64e4594903a2d1eea2ebfa60633f07 /doc
parent9b91db825484f8e16ce5d1bb3daee6e6a8151206 (diff)
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/copy_doesn__39__t_scale.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/bugs/copy_doesn__39__t_scale.mdwn b/doc/bugs/copy_doesn__39__t_scale.mdwn
new file mode 100644
index 000000000..1a83ae548
--- /dev/null
+++ b/doc/bugs/copy_doesn__39__t_scale.mdwn
@@ -0,0 +1,4 @@
+It seems that git-annex copies every individual file in a separate transaction. This is quite costly for mass transfers: each file involves a separate rsync invocation and the creation of a new commit. Even with a meager thousand files or so in the annex, I have to wait for fifteen minutes to copy the contents to another disk, simply because every individual file involves some disk thrashing. Also, it seems suspicious that the git-annex branch would get a thousands commits of history from the simple procedure of copying everything to a new repository. Surely it would be better to first copy everything and then create only a single commit that registers the changes to the files' availability?
+
+(I'm also not quite clear on why rsync is being used when both repositories are local. It seems to be just overhead.)
+