From: Bruno Haible <bruno@clisp.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: how to speed up "git log"?
Date: Mon, 12 Feb 2007 12:27:15 +0100 [thread overview]
Message-ID: <200702121227.15757.bruno@clisp.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702112009440.8424@woody.linux-foundation.org>
Linus,
> > git-1.4.4: 25 seconds real time, 24 seconds of CPU time (12 user, 12 system)
> > git-1.5.0: 50 seconds real time, 39 seconds of CPU time (20 user, 19 system)
>
> That's an interesting fact in itself.
Sorry, these measurements happened to be done in different conditions:
repo fully cached in RAM vs. repo not yet in buffer cache / page cache.
When measured under the same conditions, no speed difference is visible
between git-1.4.4 and git-1.5.0-rc4.
Bruno
next prev parent reply other threads:[~2007-02-12 11:21 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
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 [this message]
[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=200702121227.15757.bruno@clisp.org \
--to=bruno@clisp.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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.