From ccdb234a0e47bb6c8f0222cd4869f07b905d83fa Mon Sep 17 00:00:00 2001
From: pat <pat@web>
Date: Thu, 7 Jul 2022 07:09:46 +0000
Subject: [PATCH]

---
 ..._status_is_slow_twice__44___then_fast.mdwn | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 doc/forum/git_status_is_slow_twice__44___then_fast.mdwn

diff --git a/doc/forum/git_status_is_slow_twice__44___then_fast.mdwn b/doc/forum/git_status_is_slow_twice__44___then_fast.mdwn
new file mode 100644
index 0000000000..e09198371d
--- /dev/null
+++ b/doc/forum/git_status_is_slow_twice__44___then_fast.mdwn
@@ -0,0 +1,21 @@
+I don't know if this is a git thing, or a git annex thing, but it's weird.
+
+After I add a bunch of files to the annex (and there are many more local files not yet added), `git status` is slow. That's not really a surprise. It shows the `refresh index` calculation as usual.
+
+I run it a second time, and I get the exact same result:
+
+```
+% time git status
+Refresh index: 100% (2997/2997), done.
+<snip>
+
+git status  38.64s user 42.08s system 80% cpu 1:39.95 total
+```
+
+I run it a third time and it's _instant_.
+
+This happens reliably. Two slow runs, and then a fast run.
+
+I don't love the initial slow run, but it makes sense, so I can live with it. The second slow run doesn't make sense to me though. Is there any way to avoid it? I guess I would expect the first slow run to refresh the index and speed up subsequent runs.
+
+- @pat