On Sun, Jun 15, 2014 at 08:05:04AM +0200, Cyril Bonté wrote: > Hi Willy, > > On 15/06/2014 07:10, Willy Tarreau wrote: > >>And not surprisingly I am experiencing delays as well when trying to clone > >> > >> http://git.haproxy.org/git/haproxy.git > > > >It should not be slow at all. > >I checked locally to ensure that there was no forwarding to the development > >server and it was fast : > > > >willy@flx02:~$ mkdir test > >willy@flx02:~$ cd test > >willy@flx02:~/test$ time git clone -q > >http://git.haproxy.org/git/haproxy.git > > > >real 0m41.569s > >user 0m31.514s > >sys 0m3.984s > >willy@flx02:~/test$ > > > >I just repacked the whole tree and it slightly sped up the clone since > >there > >are slightly less exchanges to fetch objects : > > > >willy@flx02:~/test$ time git clone -q > >http://git.haproxy.org/git/haproxy.git > > > >real 0m27.484s > >user 0m25.898s > >sys 0m0.520s > > > >Maybe it will be better for you. > > Just for information, currently I can clone the repository in around 49 > seconds.
OK, I don't think we'll go much lower given that above there were already 26 seconds of CPU on the client side. > But yesterday, when Sasha sent his email, I also made some tests : > > $ time git clone -q http://git.haproxy.org/git/haproxy.git/ > > real 4m37.767s > user 0m27.260s > sys 0m23.252s I'm not surprized, the repository had a ton of objects and had not been repacked in a year or so. Regards, Willy
