It should be caused by the I/O cache of the operating system. If your warehouse is large and there are many files in the workspace, git will have to read more data, so it will be slower. After the first read, the operating system will cache the relevant data in the disk, because it has been read into the memory anyway. If it is not needed, it would be better to keep it for the next time. After a while, this part of the cache will be replaced by new data, so it will be slow again.
Try git status -uno to see if it will be faster. See man git-status.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It should be caused by the I/O cache of the operating system. If your warehouse is large and there are many files in the workspace, git will have to read more data, so it will be slower. After the first read, the operating system will cache the relevant data in the disk, because it has been read into the memory anyway. If it is not needed, it would be better to keep it for the next time. After a while, this part of the cache will be replaced by new data, so it will be slow again.
Try git status -uno to see if it will be faster. See
man git-status.Try closing anti-virus software such as 360baidu