From bec63186ea0b9b25e2387685c209578bc316397d Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" Date: Sun, 27 Mar 2011 20:14:47 +0000 Subject: [PATCH] --- doc/forum/batch_check_on_remote_when_using_copy.mdwn | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/forum/batch_check_on_remote_when_using_copy.mdwn b/doc/forum/batch_check_on_remote_when_using_copy.mdwn index 355d98f04b..0f20ab6454 100644 --- a/doc/forum/batch_check_on_remote_when_using_copy.mdwn +++ b/doc/forum/batch_check_on_remote_when_using_copy.mdwn @@ -2,4 +2,7 @@ When I copy my local repository with SHA* to a remote repo with SHA*, every sing 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