mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2019-09-20 12:44:15 -04:00
parent 2282ba0206
commit 829ba8e77b
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/bugs/git_status_extremely_slow_with_v7/comment_2_ff005cadcae59b81c3417742b6e04261._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2019-09-20T16:25:25Z"
content="""
Once git has learned that the unlocked files are unmodified, it won't check
them again.
When you clone a repository, git checks out all the unlocked files
as pointer files, and so git's index contains their inodes, and so
no, git status is not slow in that situation.
I think you must have unlocked 1000 files, and then ran git status.
Then it would run git-annex 1000 times to smudge them all.
([[todo/git_smudge_clean_interface_suboptiomal]]).
I benchmarked that scenario to take around 28 seconds on an SSD.
Perhaps you have an old version of git before 2.5? It used to force
the entire content of each large file through a pipe to git-annex.
"""]]