summaryrefslogtreecommitdiff
path: root/doc/forum/batch_check_on_remote_when_using_copy.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/batch_check_on_remote_when_using_copy.mdwn')
-rw-r--r--doc/forum/batch_check_on_remote_when_using_copy.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/batch_check_on_remote_when_using_copy.mdwn b/doc/forum/batch_check_on_remote_when_using_copy.mdwn
new file mode 100644
index 000000000..0f20ab645
--- /dev/null
+++ b/doc/forum/batch_check_on_remote_when_using_copy.mdwn
@@ -0,0 +1,8 @@
+When I copy my local repository with SHA* to a remote repo with SHA*, every single file is checked by itself which seems rather inefficient. When my remote is accessed via ssh, git-annex opens a new connections for every check. If you are not using a ssh key or key agent, this gets tedious...
+
+For all locked files, either git's built-in mechanisms should be used or, if that's not possible, a few hundred checksums (assuming SHA* backend) should be transfered at once and then checked locally before deciding that to transfer.
+
+Once all checks are done, one single transfer session should be started. Creating new sessions and waiting for TCP's slowstart to get going is a lot less than efficient.
+
+
+-- RichiH