From: Nicolas Pitre <nico@cam.org>
To: Nick Edelen <sirnot@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Michael J Gruber <git@drmicha.warpmail.net>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Sam Vilain <sam@vilain.net>,
"Shawn O. Pearce" <spearce@spearce.org>,
Andreas Ericsson <exon@op5.se>,
Christian Couder <christian@couder.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 0/5] Suggested for PU: revision caching system to significantly speed up packing/walking
Date: Fri, 07 Aug 2009 00:42:14 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0908070036450.16073@xanadu.home> (raw)
In-Reply-To: <c77435a80908061330h2461012at8b877970cab4906b@mail.gmail.com>
On Thu, 6 Aug 2009, Nick Edelen wrote:
> Hrmm, I just realized that it dosn't actually cache paths/names...
> This obviously has no bearing on its use in packing, but I should
> either add that in or restrict usage in non-packing-related walks.
> Weird how things like that escape you.
Actually it is really the packing related walk that would benefit the
most from this work. The "counting objects" phase of a clone may take
quite a while with some repositories. Most other operations don't care
as much because the rev walk is done incrementally whereas the packing
operation needs to perform it all up front.
Nicolas
next prev parent reply other threads:[~2009-08-07 4:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 9:55 [PATCH 0/5] Suggested for PU: revision caching system to significantly speed up packing/walking Nick Edelen
2009-08-06 14:48 ` Johannes Schindelin
2009-08-06 14:58 ` Michael J Gruber
2009-08-06 17:39 ` Nick Edelen
2009-08-06 19:06 ` Johannes Schindelin
2009-08-06 20:01 ` Nick Edelen
2009-08-06 20:30 ` Nick Edelen
2009-08-06 20:32 ` Shawn O. Pearce
2009-08-06 23:35 ` A Large Angry SCM
2009-08-06 23:37 ` Shawn O. Pearce
2009-08-06 23:43 ` A Large Angry SCM
2009-08-07 0:15 ` Nick Edelen
2009-08-07 6:05 ` Johannes Schindelin
2009-08-07 4:42 ` Nicolas Pitre [this message]
2009-08-07 2:47 ` Sam Vilain
2009-08-07 4:35 ` Nicolas Pitre
2009-08-07 6:08 ` Johannes Schindelin
2009-08-07 14:18 ` Nicolas Pitre
2009-08-08 15:18 ` Johannes Schindelin
2009-08-08 16:07 ` Junio C Hamano
2009-08-08 23:54 ` Sam Vilain
2009-08-09 2:37 ` Nicolas Pitre
2009-08-09 13:42 ` Nick Edelen
2009-08-07 6:12 ` Johannes Schindelin
2009-08-07 15:00 ` Nicolas Pitre
2009-08-07 22:02 ` Nick Edelen
2009-08-07 22:48 ` Junio C Hamano
2009-08-07 22:53 ` Nick Edelen
2009-08-08 3:11 ` Junio C Hamano
2009-08-08 7:27 ` Nick Edelen
2009-08-08 7:30 ` Jeff King
2009-08-08 7:40 ` Nick Edelen
2009-08-08 2:50 ` Jeff King
2009-08-08 18:57 ` Junio C Hamano
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=alpine.LFD.2.00.0908070036450.16073@xanadu.home \
--to=nico@cam.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian@couder.net \
--cc=exon@op5.se \
--cc=git@drmicha.warpmail.net \
--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).