From: Linus Torvalds <torvalds@osdl.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, Sam Ravnborg <sam@ravnborg.org>,
git@vger.kernel.org
Subject: Re: dumb transports not being welcomed..
Date: Tue, 13 Sep 2005 17:57:22 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0509131742240.26803@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0509140152160.24606@wgmdd8.biozentrum.uni-wuerzburg.de>
On Wed, 14 Sep 2005, Johannes Schindelin wrote:
>
> IMHO the culprit is git-rev-list, which takes ages and ages for big
> repositories (beware: this could be my Darwin client which might be
> incapable to stop the rev enumeration in time; but if that can be done
> unintentionally, this can be intentionally, too!).
Packed too?
git-rev-list will take a long time if the tree is unpacked and not in the
cache. It's all disk seeks. That's _especially_ true of a full clone
(which will walk the whole way down).
But I have tons of memory in my machines, and I haven't looked at how
badly it does if you don't have that. I know that master.kernel.org is
certainly not having any trouble at all with me pulling from lots of
trees.. Maybe git-rev-list uses up lots of your memory.
I'm seeing 14 seconds of CPU-time for a _full_ kernel history, with
"--objects". Yes, it's not exactly cheap, and maybe I should optimize it
(it's all in the "--objects" handling and probably a large portion of it
is because trees actually pack very well indeed, so it's actually
unpacking a lot of trees), but considering that that is preparing the
metadata for pulling down a hundred megs of stuff..
That said, I do think that --objects handling is _very_ CPU-hungry. The
offender is this old commit of mine:
4311d328fee11fbd80862e3c5de06a26a0e80046
Author: Linus Torvalds <torvalds@g5.osdl.org>
Date: Sat Jul 23 10:01:49 2005 -0700
Be more aggressive about marking trees uninteresting
...
which is much better about avoiding objects in old trees, but it does so
at the expense of being _horribly_ CPU-inefficient. It will walk through
every tree of every commit that we decided was uninteresting.
You can try to just undo that one commit - it will make pack-files have a
few extraneous objects, but I think it will make a huge difference in the
CPU cost of "small pulls" (it won't matter at all for the "git clone"
case: for that case we just always have to walk the whole object tree).
Linus
next prev parent reply other threads:[~2005-09-14 0:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 21:07 dumb transports not being welcomed Junio C Hamano
2005-09-13 21:14 ` Sam Ravnborg
2005-09-13 21:30 ` Junio C Hamano
2005-09-13 21:42 ` Sam Ravnborg
2005-09-13 22:03 ` Horst von Brand
2005-09-13 22:23 ` Junio C Hamano
2005-09-13 22:11 ` Junio C Hamano
2005-09-13 22:21 ` Jeff Garzik
2005-09-13 22:29 ` Junio C Hamano
2005-09-14 13:21 ` Jeff Garzik
2005-09-13 22:29 ` Linus Torvalds
2005-09-13 22:37 ` Junio C Hamano
2005-09-13 22:55 ` Linus Torvalds
2005-09-13 23:02 ` Junio C Hamano
2005-09-14 2:25 ` Kay Sievers
2005-09-14 3:32 ` Junio C Hamano
2005-09-14 0:01 ` Johannes Schindelin
2005-09-14 0:57 ` Linus Torvalds [this message]
2005-09-14 1:42 ` Linus Torvalds
2005-09-14 8:38 ` Johannes Schindelin
2005-09-14 15:07 ` Linus Torvalds
2005-09-15 9:17 ` Junio C Hamano
2005-09-14 10:45 ` Sven Verdoolaege
2005-09-14 16:14 ` Junio C Hamano
2005-09-14 14:10 ` Jon Loeliger
2005-09-14 19:00 ` Junio C Hamano
2005-09-14 19:13 ` Jon Loeliger
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=Pine.LNX.4.58.0509131742240.26803@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=sam@ravnborg.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.
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).