From: demerphq <demerphq@gmail.com>
To: git@vger.kernel.org
Subject: Very slow clone time over http
Date: Fri, 19 Dec 2008 23:33:08 +0100 [thread overview]
Message-ID: <9b18b3110812191433l4eb70ccdw8693037045823aef@mail.gmail.com> (raw)
Hi,
I've been working on the migration of the perl5 repositories from
perforce to git, which is soon to be officially released.
We have set up a server with http/git/ssh access, and we had hoped
also rsync access.
However, it appears that clone using the rsync:// protocol is broken,
and now we are discovering that http cloning is extremely slow. I
reported our experiences with rsync in a previous mail, and now im
reporting the http performance issue.
When we strace the clone we observe (to quote our sysadmin):
"git seems to be stuck for 10 minutes after downloading"
"no output, strace shows it's having sex with the memory allocator"
"sex with memory allocator" ==> loads of memory allocation/dealoccation
A provisional release of the conversion is available at
http://dromedary.booking.com/perl.git
We are using git 1.6.0.5 on another more or less equivalent host, with
the same problems, and dromedary is using git version
1.6.0.4.724.ga0d3a. However we believe that the problem is actually on
the client side. The pack download itself appears to be quite fast,
however there is an extremely long pause (minutes) after which a HUGE
amount of essentially imcomprehensible output is generated about
walking packs or some such.
Timing a clone via http gets us number like:
real 7m42.459s
user 3m42.154s
sys 0m12.641s
Wheras using the git:// protocol gets us times like:
real 4m6.162s
user 0m43.595s
sys 0m4.852s
The client these numbers are from is git version 1.6.0.3.
So it take approximately twice the time via http as it does via git.
This seems somewhat strange. Is there anything we can do to improve
this? Repack? Anything like that?
A post about the github system suggests that this is not an isolated problem.
http://github.com/blog/92-http-cloning
if there is anything we can do to help resolve this issue please let us know.
cheers,
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
reply other threads:[~2008-12-19 22:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9b18b3110812191433l4eb70ccdw8693037045823aef@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).