forum/Please diagnose: `git status` is slow after updategit-annexhttp://git-annex.branchable.com/forum/Please_diagnose__58_____96__git_status__96___is_slow_after_update/git-annexikiwiki2022-03-16T16:10:51ZNow it's working normally againhttp://git-annex.branchable.com/forum/Please_diagnose__58_____96__git_status__96___is_slow_after_update/comment_1_68429f9e44ce24250c608da8ffffe643/ainohzoa2022-01-14T21:10:13Z2022-01-14T21:10:13Z
After running a <code>git status</code> today (the first time running it was slow as usual) the problem seems to have gone away. Perhaps it just needed to rebuild some kind of cache or something. I believe that I had waited for a <code>git status</code> command to completely finish before, so maybe it takes several tries to resolve this performance problem? Or possibly I'm misremembering and I never actually waited for the <code>git status</code> command to fully finish. I'm baffled by this, but happy that it's back to normal. I'll post an update if the problem comes back.
comment 2http://git-annex.branchable.com/forum/Please_diagnose__58_____96__git_status__96___is_slow_after_update/comment_2_cefd5742da29e19f5ab3406698a13f9f/joey2022-01-25T17:21:20Z2022-01-25T16:36:20Z
<p>git can sometimes get into a situation where it is unsure about the status
of working tree files, and when those files are not git-annex symlinks but
either unlocked git-annex files or regular files checked into git, it needs
to run <code>git-annex smudge</code> once per file. That can take a long time when it
somehow needs to check many files.</p>
<p>This kind of slowdown is largely avoided by setting:</p>
<pre><code>git config filter.annex.process 'git-annex filter-process'
</code></pre>
<p>Which will be handled automatically by a future upgrade.</p>
I have seen thishttp://git-annex.branchable.com/forum/Please_diagnose__58_____96__git_status__96___is_slow_after_update/comment_3_ab005dba805922597a533ddd661f20c8/Gus2022-03-16T16:10:51Z2022-03-16T16:10:51Z
<p><code>git-annex sync</code> has been very slow on one of my repositories the last few times I ran it. An operation that used to run in well less than a minute (via USB 2.0) was now taking upwards of one hour. I do have many files there that are not being tracked by git.</p>
<p>I followed <em>ainohzoa</em>'s description to confirm I was seeing the same issue and tried the process that worked for them: running <code>git status</code> twice. Although it took a few hours to complete, things went back to normal after that. Thank you, <em>ainohzoa</em>.</p>