All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: git@vger.kernel.org
Subject: git pull takes ~8 seconds on up-to-date Linux git tree
Date: Thu, 4 Oct 2012 16:14:54 +0200	[thread overview]
Message-ID: <20121004141454.GA246@x4> (raw)

Hi,

with current trunk I get the following on an up-to-date Linux tree:

markus@x4 linux % time git pull
Already up-to-date.
git pull  7.84s user 0.26s system 92% cpu 8.743 total

git version 1.7.12 is much quicker:

markus@x4 linux % time git pull
Already up-to-date.
git pull  0.10s user 0.02s system 16% cpu 0.740 total

perf shows for trunk:

    22.11%  git-merge  libz.so.1.2.7          [.] 0x00000000000073bc           
    22.03%        git  libz.so.1.2.7          [.] 0x0000000000007338           
    14.18%        git  libz.so.1.2.7          [.] inflate                      
    13.70%  git-merge  libz.so.1.2.7          [.] inflate                      
     9.18%        git  git                    [.] 0x00000000000ea391           
     8.56%  git-merge  git-merge              [.] 0x00000000000f0598           
     1.58%  git-merge  libz.so.1.2.7          [.] adler32                      
     1.52%        git  libz.so.1.2.7          [.] adler32                      
     0.59%        git  [kernel.kallsyms]      [k] clear_page_c

and for 1.7.12:

    39.29%        git  git                    [.] 0x00000000000b9fa8           
    12.16%        git  libz.so.1.2.7          [.] inflate                      
     8.67%        git  libz.so.1.2.7          [.] 0x000000000000a18e           
     8.49%  git-merge  git-merge              [.] 0x00000000000efa15           
     4.96%        git  libc-2.16.90.so        [.] memcpy@@GLIBC_2.14           
     2.63%        git  libc-2.16.90.so        [.] _int_malloc                  
     2.61%  git-merge  [kernel.kallsyms]      [k] clear_page_c                 
     2.32%        git  [kernel.kallsyms]      [k] clear_page_c                 
     2.04%        git  [kernel.kallsyms]      [k] filemap_fault                
     1.87%  git-merge  libc-2.16.90.so        [.] memcpy@@GLIBC_2.14  

-- 
Markus

             reply	other threads:[~2012-10-04 22:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 14:14 Markus Trippelsdorf [this message]
2012-10-04 18:43 ` git pull takes ~8 seconds on up-to-date Linux git tree Jeff King
2012-10-04 19:26   ` Markus Trippelsdorf
2012-10-04 19:36   ` Junio C Hamano
2012-10-04 20:03   ` Junio C Hamano
2012-10-04 20:44     ` Junio C Hamano
2012-10-04 21:16   ` Junio C Hamano
2012-10-04 21:28     ` Junio C Hamano
2012-10-04 22:37       ` Junio C Hamano
2012-10-05 20:34         ` Junio C Hamano
2012-10-05 23:21           ` Jeff King
2012-10-06  5:20             ` Junio C Hamano
2012-10-06 12:57               ` Jeff King

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=20121004141454.GA246@x4 \
    --to=markus@trippelsdorf.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.