From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Uri Moszkowicz <uri@4refs.com>
Cc: git@vger.kernel.org
Subject: Re: Long clone time after "done."
Date: Wed, 24 Oct 2012 11:29:00 +0700 [thread overview]
Message-ID: <CACsJy8DvNSVSUT_9ym52pVaDSNMk10WfaVGhfgQeC8+SOWSpEw@mail.gmail.com> (raw)
In-Reply-To: <CAMJd5AQBbnFqT5xrFuPOEsJevwDE=jUgBVFZ5KqTZk5zv5+NOw@mail.gmail.com>
On Wed, Oct 24, 2012 at 1:30 AM, Uri Moszkowicz <uri@4refs.com> wrote:
> I have a large repository which I ran "git gc --aggressive" on that
> I'm trying to clone on a local file system. I would expect it to
> complete very quickly with hard links but it's taking about 6min to
> complete with no checkout (git clone -n). I see the message "Clining
> into 'repos'... done." appear after a few seconds but then Git just
> hangs there for another 6min. Any idea what it's doing at this point
> and how I can speed it up?
"done." is printed by clone_local(), which is called in cmd_clone().
After that there are just a few more calls. Maybe you could add a few
printf in between these calls, see which one takes most time?
--
Duy
next prev parent reply other threads:[~2012-10-24 4:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 18:30 Long clone time after "done." Uri Moszkowicz
2012-10-24 4:29 ` Nguyen Thai Ngoc Duy [this message]
2012-10-24 17:14 ` Uri Moszkowicz
2012-11-07 17:32 ` Uri Moszkowicz
2012-11-08 15:56 ` Jeff King
2012-11-08 17:20 ` Uri Moszkowicz
2012-11-08 20:33 ` Jeff King
2012-11-08 21:49 ` Uri Moszkowicz
2012-11-08 22:11 ` Jeff King
2012-11-08 22:16 ` Uri Moszkowicz
2012-11-08 22:33 ` Jeff King
2012-11-08 23:35 ` Uri Moszkowicz
2012-11-26 18:06 ` Uri Moszkowicz
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACsJy8DvNSVSUT_9ym52pVaDSNMk10WfaVGhfgQeC8+SOWSpEw@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=uri@4refs.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).