From 9136d3c86f37107aa938ef953957ea9a0546eaec Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 9 Apr 2015 13:45:47 -0400 Subject: [PATCH] comment --- ...ent_3_8d9e5a1aef2648d7a844623e6237d551._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/Why_is_git_annex_status_slow__63__/comment_3_8d9e5a1aef2648d7a844623e6237d551._comment diff --git a/doc/forum/Why_is_git_annex_status_slow__63__/comment_3_8d9e5a1aef2648d7a844623e6237d551._comment b/doc/forum/Why_is_git_annex_status_slow__63__/comment_3_8d9e5a1aef2648d7a844623e6237d551._comment new file mode 100644 index 0000000000..54d2b24c49 --- /dev/null +++ b/doc/forum/Why_is_git_annex_status_slow__63__/comment_3_8d9e5a1aef2648d7a844623e6237d551._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-04-09T17:44:01Z" + content=""" +The sizes of the files should not affect how fast git-annex status runs. + +But, direct mode certianly does. git-annex has to do significantly more +work in direct mode to figure out the status of a file. Including querying +git. In indirect mode, it can just stat the symlink and see if its content +is present, which is much faster. + +(There's probably also some other inneficiencies in Windows.) +"""]]