From: Jeff King <peff@peff.net>
To: Uri Moszkowicz <uri@4refs.com>
Cc: git@vger.kernel.org
Subject: Re: Long clone time after "done."
Date: Thu, 8 Nov 2012 15:33:32 -0500 [thread overview]
Message-ID: <20121108203332.GQ15560@sigill.intra.peff.net> (raw)
In-Reply-To: <CAMJd5AQ24u11BH6rMAHvR95N4ys6KHfEQKD1uLzr+=TDgN_69Q@mail.gmail.com>
On Thu, Nov 08, 2012 at 11:20:29AM -0600, Uri Moszkowicz wrote:
> I tried the patch but it doesn't appear to have helped :( Clone time
> with it was ~32m.
That sounds ridiculously long.
> Do you all by any chance have a tool to obfuscate a repository?
> Probably I still wouldn't be permitted to distribute it but might make
> the option slightly more palatable. Anything else that I can do to
> help debug this problem?
I don't have anything already written. What platform are you on? If it's
Linux, can you try using "perf" to record where the time is going?
How many refs do you have? What does:
echo "heads: $(git for-each-ref refs/heads | wc -l)"
echo " tags: $(git for-each-ref refs/tags | wc -l)"
report? How long does it take to look up a tag, like:
time git cat-file tag refs/tags/some-tag
?
-Peff
next prev parent reply other threads:[~2012-11-08 20:33 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
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 [this message]
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=20121108203332.GQ15560@sigill.intra.peff.net \
--to=peff@peff.net \
--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).