|Re: Very slow git clone performance [message #1755411 is a reply to message #1755410]
||Fri, 03 March 2017 07:25
| Malte Brunnlieb
Registered: February 2011
> Did you try to clone the same repository using native git command line ?|
> Is this also slow ?
Basically, it is the same until the git bash as well as the console output of eclipse/oomph states 100% fetching. After that it takes a second for git bash and multiple minutes for oomph/eclipse to finish. Whatever is done after fetching all change sets. I do not know.
> Does the upstream repository have many refs ?
See my post: git rev-list --all --count = 1229
> Is the upstream repository gc'ed on a regular schedule ?
remote? It is a private GitHub repository. I do not know what github is automatically performing on it. I did not see any configuration option for that.
> Does the upstream repository have bitmap indexes (can be configured in gc configuration) ?
Sounds interesting, but I did not see any option for that on GitHub. But just to show you some more measures of the repository:
remote: Counting objects: 19343, done.
remote: Compressing objects: 100% (27/27), done.
remote: Total 19343 (delta 3), reused 0 (delta 0), pack-reused 19312
Receiving objects: 100% (19343/19343), 3.55 MiB | 105.00 KiB/s, done.
Resolving deltas: 100% (8095/8095), done.
I even not entirely convinced that a repack would fix this as the repository seems to be quite normal from the number of objects etc.
Powered by FUDForum
. Page generated in 0.01919 seconds