git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: A Large Angry SCM <gitzilla@gmail.com>
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, 6 Aug 2009 16:37:39 -0700	[thread overview]
Message-ID: <20090806233739.GL1033@spearce.org> (raw)
In-Reply-To: <4A7B68C4.8070406@gmail.com>

A Large Angry SCM <gitzilla@gmail.com> wrote:
> Shawn O. Pearce wrote:
>> Nick Edelen <sirnot@gmail.com> wrote:
>>> Hrmm, I just realized that it dosn't actually cache paths/names...
>>
>> You may not need the path name, but instead the hash value that
>> pack-objects computes from the path name.
>
> 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.

This is a local cache.  If there was a version number in the header,
and the hash function changes, we could just bump the version number
and invalidate all of the caches.

No sense in storing (and doing IO of) huge duplicate string values
for something where we really only need 32 bits, and where a
recompute from scratch only costs a minute.

-- 
Shawn.

  reply	other threads:[~2009-08-06 23:37 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 [this message]
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=20090806233739.GL1033@spearce.org \
    --to=spearce@spearce.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=gitzilla@gmail.com \
    --cc=peff@peff.net \
    --cc=sam@vilain.net \
    --cc=sirnot@gmail.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 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).