From 65b03584448230f461596df59dadb7487e94c684 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 7 Jan 2016 18:22:51 -0400 Subject: [PATCH] response --- ..._8a9b5bc3b8a8ef947f2620422307c465._comment | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 doc/forum/Massive_drop_in_performance_with_--jobs_option/comment_2_8a9b5bc3b8a8ef947f2620422307c465._comment diff --git a/doc/forum/Massive_drop_in_performance_with_--jobs_option/comment_2_8a9b5bc3b8a8ef947f2620422307c465._comment b/doc/forum/Massive_drop_in_performance_with_--jobs_option/comment_2_8a9b5bc3b8a8ef947f2620422307c465._comment new file mode 100644 index 0000000000..b00eb61a0b --- /dev/null +++ b/doc/forum/Massive_drop_in_performance_with_--jobs_option/comment_2_8a9b5bc3b8a8ef947f2620422307c465._comment @@ -0,0 +1,27 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2016-01-07T22:13:14Z" + content=""" +Version 5.20151019 is right between the two versions given, and probably +contains the reason for the drop in performance: That version started +checksumming files after receiving them to verify that their content is +good. + +If so, this will get back the old level of performance: + + git config annex.verify false + +If the performance problem were actually related to the new progress +display, passing --quiet will disable that display. If you can show that +simply passing --quiet speeds up transfers significantly somehow, +I'd be happy to investigate further. + + +---- + +@umeboshi I don't think your comment is really related to the original question. +If you run gets of a bunch of files in parallel, and two of the files +have the same content, you can get this situation where a transfer of +the content is already in progress. +"""]]