From: A Large Angry SCM <gitzilla@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Nick Edelen <sirnot@gmail.com>,
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>, 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: Thu, 06 Aug 2009 19:35:32 -0400 [thread overview]
Message-ID: <4A7B68C4.8070406@gmail.com> (raw)
In-Reply-To: <20090806203223.GK1033@spearce.org>
Shawn O. Pearce wrote:
> Nick Edelen <sirnot@gmail.com> 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.
>>
>> I think I may go ahead and add support for this tomorrow. It should
>> have no effect on performance and very little impact on cache slice
>> size.
>
> You may not need the path name, but instead the hash value that
> pack-objects computes from the path name. All that matters is
> the hash, so pack-objects can schedule the objects into the right
> buckets when its doing delta computation for objects which are not
> yet delta compressed, or whose delta cannot be suitably reused.
>
Please do NOT expose the hash values. The hash used by pack-objects is
an implementation detail of the heuristics used by the _current_ object
packing code. It would be a real shame to have to maintain backward
compatibility with it at some future date after the packing machinery
has changed.
next prev parent reply other threads:[~2009-08-06 23:36 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 [this message]
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
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=4A7B68C4.8070406@gmail.com \
--to=gitzilla@gmail.com \
--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 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.