From: Joey Hess <joey@kitenet.net>
To: Jeff King <peff@peff.net>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: speed of git reset -- file
Date: Wed, 1 Jun 2011 19:31:57 -0400 [thread overview]
Message-ID: <20110601233157.GA2468@gnu.kitenet.net> (raw)
In-Reply-To: <20110601225647.GD16820@sigill.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
Jeff King wrote:
> OK, that's horrific. For me, the stat information for linux-2.6 all sits
> in cache and it takes about 0.3 seconds to refresh the index. I have 8G
> of ram and a nice SSD, though it doesn't actually hit the disk at all.
>
> Is it really faulting the stat information from disk that takes so long?
> Have you tried running "perf" on "git update-index --refresh"?
Cold cache:
Performance counter stats for 'git update-index --refresh':
9725.574501 task-clock-msecs # 0.337 CPUs
58,163 context-switches # 0.006 M/sec
94 CPU-migrations # 0.000 M/sec
8,637 page-faults # 0.001 M/sec
12,825,956,531 cycles # 1318.787 M/sec (scaled from 33.43%)
2,696,089,912 instructions # 0.210 IPC (scaled from 50.03%)
457,705,110 branches # 47.062 M/sec (scaled from 51.30%)
40,033,685 branch-misses # 8.747 % (scaled from 50.19%)
149,071,234 cache-references # 15.328 M/sec (scaled from 32.83%)
9,662,661 cache-misses # 0.994 M/sec (scaled from 32.27%)
28.846625099 seconds time elapsed
Warm cache is 0.88 seconds, but cold cache is typical; I use a cheap netbook
for a lot of different stuff.
Also, I can get much worse cold cache numbers on eg, a fairly average
VPS node, where it takes > 1 minute.
--
see shy jo
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-06-01 23:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 19:00 speed of git reset -- file Joey Hess
2011-05-31 21:26 ` Jeff King
2011-05-31 21:54 ` Junio C Hamano
2011-05-31 22:13 ` Jeff King
2011-05-31 22:13 ` Matthieu Moy
2011-06-01 1:14 ` Nguyen Thai Ngoc Duy
2011-05-31 23:39 ` Junio C Hamano
2011-06-01 19:58 ` Jeff King
2011-06-01 20:16 ` Joey Hess
2011-06-01 21:18 ` Jeff King
2011-06-01 22:05 ` Joey Hess
2011-06-01 22:56 ` Jeff King
2011-06-01 23:31 ` Joey Hess [this message]
2011-06-02 3:18 ` Jeff King
2011-06-02 4:36 ` Joey Hess
2011-06-02 4:46 ` Joey Hess
2011-06-01 20:51 ` 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=20110601233157.GA2468@gnu.kitenet.net \
--to=joey@kitenet.net \
--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.
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).