From: David Woodhouse <dwmw2@infradead.org>
To: git@vger.kernel.org
Subject: Why is git-clone --reference so slow?
Date: Mon, 05 Feb 2007 11:46:44 +0000 [thread overview]
Message-ID: <1170676004.29759.767.camel@pmac.infradead.org> (raw)
My DSL line sucks; I know this. But why is git-clone so bad at using it?
This is slow and seems to be downloading a lot of stuff it doesn't
need...
pmac /pmac/git $ git-clone --reference /pmac/git/linux-2.6 git://git.kernel.org/pub/scm/linux/kernel/git/geoff/ps3-linux.git
remote: Generating pack...
remote: Done counting 14428 objects.
remote: Deltifying 14428 objects.
remote: 100% (14428/14428) done
Indexing 14428 objects.
25% (3662/14428) done
At this point I got bored and hit ^C, then logged in to hera and did it
there, then rsync'd the result...
hera /home/dwmw2/x $ git-clone -n --bare --reference /pub/scm/linux/kernel/git/torvalds/linux-2.6.git /pub/scm/linux/kernel/git/geoff/ps3-linux.git
remote: Generating pack...
remote: Done counting 14490 objects.
remote: Deltifying 14490 objects.
remote: 100% (14490/14490) done
Indexing 14490 objects.
remote: Total 14490, written 14490 (delta 579), reused 5598 (delta 367)
100% (14490/14490) done
Resolving 579 deltas.
100% (579/579) done
pmac /pmac/git/ps3-linux $ rsync -avz master.kernel.org:/home/dwmw2/x/ps3-linux/ .git
pmac /pmac/git/ps3-linux $ echo /pmac/git/linux-2.6/.git/objects > .git/objects/info/alternates
That was a _lot_ faster, and abused my poor DSL line a lot less. Why's
git so bad at it?
--
dwmw2
next reply other threads:[~2007-02-05 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 11:46 David Woodhouse [this message]
2007-02-05 15:31 ` Why is git-clone --reference so slow? Johannes Schindelin
2007-02-05 15:35 ` David Woodhouse
2007-02-07 10:03 ` Junio C Hamano
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=1170676004.29759.767.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--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).