From: Alex Riesen <raa.lkml@gmail.com>
To: Nick Edelen <sirnot@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>, Sam Vilain <sam@vilain.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Andreas Ericsson <exon@op5.se>, Jeff King <peff@peff.net>
Subject: Re: [RFC/PATCH 1/4] rev-cache: basic implementation + full docs + tests
Date: Fri, 3 Jul 2009 23:43:27 +0200 [thread overview]
Message-ID: <81b0412b0907031443r1c49e8c4r598b3cf16eb641a8@mail.gmail.com> (raw)
In-Reply-To: <op.uwhy8r14tdk399@sirnot>
On Fri, Jul 3, 2009 at 17:13, Nick Edelen<sirnot@gmail.com> wrote:
> Traversing objects is currently very costly, as every commit and tree must be loaded and parsed. Much time and energy could be saved by caching metadata and topological info in an efficient, easily accessible manner. Furthermore, this could improve git's interfacing potential, by providing a condensed summary of a repository's commit tree.
Do you have any benchmarks? How much improvement does it
mean for _common_ operations?
prev parent reply other threads:[~2009-07-03 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 15:13 [RFC/PATCH 1/4] rev-cache: basic implementation + full docs + tests Nick Edelen
2009-07-03 21:43 ` Alex Riesen [this message]
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=81b0412b0907031443r1c49e8c4r598b3cf16eb641a8@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=exon@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sam@vilain.net \
--cc=sirnot@gmail.com \
--cc=spearce@spearce.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 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).