From: Uri Moszkowicz <uri@4refs.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Long clone time after "done."
Date: Thu, 8 Nov 2012 17:35:08 -0600 [thread overview]
Message-ID: <CAMJd5AQOH=uu1c3enr5fES+Bw4FHZuP++J7-aCM2B+f_G3YMtg@mail.gmail.com> (raw)
In-Reply-To: <20121108223319.GA11734@sigill.intra.peff.net>
I tried on the local disk as well and it didn't help. I managed to
find a SUSE11 machine and tried it there but no luck so I think we can
eliminate NFS and OS as significant factors now.
I ran with perf and here's the report:
ESC[31m 69.07%ESC[m git /lib64/libc-2.11.1.so
[.] memcpy
ESC[31m 12.33%ESC[m git
<prefix>/git-1.8.0.rc2.suse11/bin/git [.]
blk_SHA1_Block
ESC[31m 5.11%ESC[m git
<prefix>/zlib/local/lib/libz.so.1.2.5 [.]
inflate_fast
ESC[32m 2.61%ESC[m git
<prefix>/zlib/local/lib/libz.so.1.2.5 [.]
adler32
ESC[32m 1.98%ESC[m git /lib64/libc-2.11.1.so
[.] _int_malloc
ESC[32m 0.86%ESC[m git [kernel]
[k] clear_page_c
Does this help? Machine has 396GB of RAM if it matters.
On Thu, Nov 8, 2012 at 4:33 PM, Jeff King <peff@peff.net> wrote:
> On Thu, Nov 08, 2012 at 04:16:59PM -0600, Uri Moszkowicz wrote:
>
>> I ran "git cat-file commit some-tag" for every tag. They seem to be
>> roughly uniformly distributed between 0s and 2s and about 2/3 of the
>> time seems to be system. My disk is mounted over NFS so I tried on the
>> local disk and it didn't make a difference.
>>
>> I have only one 1.97GB pack. I ran "git gc --aggressive" before.
>
> Ah. NFS. That is almost certainly the source of the problem. Git will
> aggressively mmap. I would not be surprised to find that RHEL4's NFS
> implementation is not particularly fast at mmap-ing 2G files, and is
> spending a bunch of time in the kernel servicing the requests.
>
> Aside from upgrading your OS or getting off of NFS, I don't have a lot
> of advice. The performance characteristics you are seeing are so
> grossly off of what is normal that using git is probably going to be
> painful. Your 2s cat-files should be more like .002s. I don't think
> there's anything for git to fix here.
>
> You could try building with NO_MMAP, which will emulate it with pread.
> That might fare better under your NFS implementation. Or it might be
> just as bad.
>
> -Peff
next prev parent reply other threads:[~2012-11-08 23:35 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
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 [this message]
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='CAMJd5AQOH=uu1c3enr5fES+Bw4FHZuP++J7-aCM2B+f_G3YMtg@mail.gmail.com' \
--to=uri@4refs.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).