From: Shawn Pearce <spearce@spearce.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: gitzilla@gmail.com, git@vger.kernel.org
Subject: Re: A look at some alternative PACK file encodings
Date: Thu, 7 Sep 2006 01:41:26 -0400 [thread overview]
Message-ID: <20060907054126.GC31580@spearce.org> (raw)
In-Reply-To: <9e4733910609061704s429c449etcf0475841556c26b@mail.gmail.com>
Jon Smirl <jonsmirl@gmail.com> wrote:
> The repack code could build a model of the tree as it is repacking,
> that is what fast-import does. If you have a model of the tree then
> when you change a TREE node you track the last sha1 that corresponded
> to that directory path. Now you know what to diff to.
Right. But that's horribly expensive. For the most part
pack-objects does a good job estimating this by hashing the trees
by their name and size into the same hash bucket. And its fast.
Besides its better to store reverse deltas (like what CVS does)
as faster access to the more recent stuff is more interesting than
faster access to the older stuff. pack-objects tries to do this
based on the order given by rev-list.
--
Shawn.
next prev parent reply other threads:[~2006-09-07 6:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 21:47 A look at some alternative PACK file encodings A Large Angry SCM
2006-09-06 23:23 ` Jon Smirl
2006-09-06 23:39 ` A Large Angry SCM
2006-09-06 23:56 ` Linus Torvalds
2006-09-07 0:10 ` Jon Smirl
2006-09-07 0:06 ` David Lang
2006-09-07 0:19 ` A Large Angry SCM
2006-09-07 0:45 ` Linus Torvalds
2006-09-07 0:37 ` Nicolas Pitre
2006-09-07 0:04 ` Jon Smirl
2006-09-07 5:41 ` Shawn Pearce [this message]
2006-09-07 5:34 ` Shawn Pearce
2006-09-07 0:40 ` Nicolas Pitre
2006-09-07 0:59 ` Jon Smirl
2006-09-07 2:30 ` Nicolas Pitre
2006-09-07 2:33 ` A Large Angry SCM
2006-09-07 1:11 ` Junio C Hamano
2006-09-07 2:47 ` Nicolas Pitre
2006-09-07 4:33 ` Shawn Pearce
2006-09-07 5:27 ` Junio C Hamano
2006-09-07 5:46 ` Shawn Pearce
2006-09-07 18:50 ` Junio C Hamano
2006-09-07 5:21 ` Shawn Pearce
[not found] ` <9e4733910609061617m6783d6c4xaca2f9575e12d455@mail.gmail.com>
2006-09-07 5:39 ` A Large Angry SCM
-- strict thread matches above, loose matches on Subject: below --
2006-09-07 8:41 linux
2006-09-07 17:20 ` Nicolas Pitre
2006-09-07 19:16 ` linux
2006-09-07 9:07 linux
2006-09-07 12:57 ` Jon Smirl
2006-09-07 13:34 ` linux
2006-09-07 14:19 ` Jon Smirl
2006-09-07 15:01 ` linux
2006-09-07 14:39 ` Richard Curnow
2006-09-07 17:40 ` Junio C Hamano
2006-09-07 17:22 ` A Large Angry SCM
2006-09-07 17:32 ` Nicolas Pitre
2006-09-07 19:22 ` linux
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=20060907054126.GC31580@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitzilla@gmail.com \
--cc=jonsmirl@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).