From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
Bruno Haible <bruno@clisp.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: how to speed up "git log"?
Date: Mon, 12 Feb 2007 01:06:41 -0500 [thread overview]
Message-ID: <20070212060641.GC699@spearce.org> (raw)
In-Reply-To: <7vmz3kaugq.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> I doubt it -- sliding mmap() in the current git, while is a good
> change overall for handling really huge repos, would most likely
> perform poorer than the fixed mmap() in 1.4.4 series on
> platforms with slow mmap(), most notably on MacOS X.
>
> It _might_ be possible that turning some sliding mmap() calls
> into pread() makes it perform better on MacOS X.
>
> I wonder what happens it git is compiled with NO_MMAP there...
So I ran three trials, v1.5.0-rc4-26-gcc46a74 with and without
NO_MMAP against v1.4.4.4 on a freshly repacked git.git.
v150-mmap:
3.33 real 3.12 user 0.05 sys
3.32 real 3.12 user 0.05 sys
3.34 real 3.12 user 0.05 sys
v150-nommap:
3.46 real 3.13 user 0.16 sys
3.43 real 3.13 user 0.16 sys
3.46 real 3.13 user 0.16 sys
v1444-mmap:
3.30 real 3.09 user 0.05 sys
3.30 real 3.09 user 0.05 sys
3.25 real 3.09 user 0.04 sys
CFLAGS="-O2"; the above timings are three representative samples
out of 10 runs each, all hot cache.
Clearly the sliding mmap window isn't hurting us in this case by
very much, and NO_MMAP really isn't helping matters at all.
--
Shawn.
next prev parent reply other threads:[~2007-02-12 6:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 11:52 how to speed up "git log"? Bruno Haible
2007-02-11 16:49 ` Johannes Schindelin
2007-02-11 23:00 ` Shawn O. Pearce
2007-02-11 23:08 ` Johannes Schindelin
2007-02-11 23:41 ` Bruno Haible
2007-02-11 23:46 ` Shawn O. Pearce
2007-02-11 23:56 ` Johannes Schindelin
2007-02-11 23:59 ` Robin Rosenberg
2007-02-12 2:02 ` Bruno Haible
2007-02-12 11:19 ` Johannes Schindelin
2007-02-12 4:08 ` Junio C Hamano
2007-02-12 6:06 ` Shawn O. Pearce [this message]
2007-02-12 6:11 ` Junio C Hamano
2007-02-12 6:22 ` Shawn O. Pearce
2007-02-12 6:28 ` Shawn O. Pearce
2007-02-12 4:20 ` Linus Torvalds
2007-02-12 11:27 ` Bruno Haible
[not found] ` <20070211152840.GA2781@steel.home>
2007-02-11 23:52 ` Bruno Haible
2007-02-17 19:19 ` Bruno Haible
2007-02-17 23:20 ` Johannes Schindelin
2007-02-18 0:09 ` piped to a pager (was: how to speed up "git log"?) Bruno Haible
2007-02-18 0:10 ` Johannes Schindelin
2007-02-18 6:33 ` how to speed up "git log"? Shawn O. Pearce
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=20070212060641.GC699@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=bruno@clisp.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=robin.rosenberg.lists@dewire.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.
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).