From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Bruno Haible <bruno@clisp.org>, git@vger.kernel.org
Subject: Re: how to speed up "git log"?
Date: Sun, 11 Feb 2007 18:00:35 -0500 [thread overview]
Message-ID: <20070211230035.GD31488@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0702111745170.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > 1) Why so much user CPU time?
>
> See above.
Some of the ideas Nico and I have kicked around for a pack v4 (post
1.5.0, obviously) would speed up revision traversal by bypassing
some of the costly decompression overheads.
> > 2) Why so much system CPU time, but only on MacOS X?
>
> Probably the mmap() problem. Does it go away when you use git 1.5.0-rc4?
What does 1.5.0-rc4 do here that didn't happen before? Are you
referring to the mmap sliding window? Because NO_MMAP might be
faster on MacOS X then using mmap (thanks to its slower mmap)... but
I can't say I have performance tested it either way.
--
Shawn.
next prev parent reply other threads:[~2007-02-11 23:00 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 [this message]
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
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=20070211230035.GD31488@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=bruno@clisp.org \
--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.