| Git Clone Wizard Very Slow Vs. Git Command Line [message #1854229] |
Mon, 08 August 2022 14:19  |
 Mike K
Messages: 2
Registered: August 2022 |
Junior Member |
|
|
Hello,
We are seeing very slow cloning times when using Git Clone Wizard versus Git command line.
For example, to clone one of our repos takes about 11 minutes using Git command line and about 137 minutes using Git command line.
There appears to be no difference in the cloned repos using the different methods.
It appears that Git Clone Wizard is performing different steps to clone versus Git command line.
The steps for Git command line can be seen in the attachment.
It's not clear what steps are being performed using Git Clone Wizard. However, I do see it's performing "Checking out files:" which is what is causing the very long clone time.
What can be done to get Git Clone Wizard to perform as well as Git command line?
Thanks.
[Updated on: Mon, 08 August 2022 16:58] Report message to a moderator |
|
|
| Re: Git Clone Wizard Very Slow Vs. Git Command Line [message #1854238 is a reply to message #1854229] |
Mon, 08 August 2022 17:48  |
Thomas Wolf
Messages: 576
Registered: August 2016 |
Senior Member |
|
|
It looks like you use LFS, and have 3069 LFS files. C git has delayed smudge filtering for such files: the LFS filter can return immediately with status "delayed", and the file is skipped for the initial checkout. LFS then continues in the background to download the (large) file. Once all normal files have been checked out, git then re-tries to get these "delayed" files. This essentially parallelizes downloading LFS files.
See "Long-Running Filter Process" in the C git documentation.
JGit has no such mechanism, its built-in LFS smudge filter is synchronous and downloads one LFS file after the other during check-out.
I suspect that this accounts for most of this time difference.
[Updated on: Mon, 08 August 2022 18:05] Report message to a moderator |
|
|
|
|
Powered by
FUDForum. Page generated in 0.04025 seconds
] 
Search
Help
Register
Login
Home
