From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Bruno Haible <bruno@clisp.org>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>, git@vger.kernel.org
Subject: Re: how to speed up "git log"?
Date: Mon, 12 Feb 2007 12:19:24 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.63.0702121215190.22628@wbgn013.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <200702120302.00576.bruno@clisp.org>
Hi,
On Mon, 12 Feb 2007, Bruno Haible wrote:
> Robin Rosenberg wrote:
> > Since you know that you are not interested in the whole history, you can limit your scan.
> >
> > git log COREUTILS-5_2_1..COREUTILS-6_4 src/tr.c
>
> Thanks, that indeed does the trick: it reduces the time from 33 sec to 11 sec.
>
> To reduce the time even more, and to allow more flexibility among the
> search criteria (e.g. "I need the commits from date X to date Y, on this
> file set, from anyone except me"), I would need to connect git to a
> database. git cannot store all kinds of indices and reverse mappings to
> allow all kinds of queries; that's really a classical database
> application area.
[in the following paragraph, "index" means the index on a classical
database table]
And -- as everywhere else with classical databases -- you have to ask if
it is worth it. Given the fact that a one-time use of such an index is
_worse_ than doing it without index at all (building and writing the
index is _at least_ as expensive as searching once without an index), I'd
rather doubt it.
However, if you do similar kinds of searches quite often, it makes tons of
sense to connect to a database. We already use sqlite in cvsserver, so I'd
try that.
Ciao,
Dscho
next prev parent reply other threads:[~2007-02-12 11:19 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 [this message]
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=Pine.LNX.4.63.0702121215190.22628@wbgn013.biozentrum.uni-wuerzburg.de \
--to=johannes.schindelin@gmx.de \
--cc=bruno@clisp.org \
--cc=git@vger.kernel.org \
--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 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.