summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://svario.it/gioele <gioele@web>2014-11-01 14:12:35 +0000
committerGravatar admin <admin@branchable.com>2014-11-01 14:12:35 +0000
commitf1d84c68cdb9666c074e64ea51ff7a5dea03dcbe (patch)
treef3b4e3d93eb34d4c87eced230acdc2a0301a52a5
parentd1f6d7e459aefb9c2f7d2e61ba9bde0831a6f8d2 (diff)
new forum post "Why is git annex status slow?"
-rw-r--r--doc/forum/Why_is_git_annex_status_slow__63__.mdwn20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/forum/Why_is_git_annex_status_slow__63__.mdwn b/doc/forum/Why_is_git_annex_status_slow__63__.mdwn
new file mode 100644
index 000000000..5c659b61d
--- /dev/null
+++ b/doc/forum/Why_is_git_annex_status_slow__63__.mdwn
@@ -0,0 +1,20 @@
+It seems that `git annex status` is much slower than `git status`, at least in direct mode. The man page does not give any hint about why it should be slower.
+
+Does `git annex status` do something that `git status` does not?
+
+Here is an example in a repo with 8000+ files in direct mode and with no modified files:
+
+
+ $ time git -c core.bare=false status --porcelain > /dev/null
+
+ real 0m0.096s
+ user 0m0.042s
+ sys 0m0.071s
+
+ $ time git annex status
+
+ real 0m17.144s
+ user 0m10.555s
+ sys 0m1.934s
+
+It is strange to see that `git annex status` is ~200 times slower than the bare `git status`.