From: Keith Packard <keithp@keithp.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: keithp@keithp.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: Repacking many disconnected blobs
Date: Wed, 14 Jun 2006 11:59:27 -0700 [thread overview]
Message-ID: <1150311567.30681.28.camel@neko.keithp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606141113130.5498@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
On Wed, 2006-06-14 at 11:18 -0700, Linus Torvalds wrote:
> You don't _need_ to shuffle. As mentioned, it will only affect the
> location of the data in the pack-file, which in turn will mostly matter
> as an IO pattern thing, not anything really fundamental. If the pack-file
> ends up caching well, the IO patterns obviously will never matter.
Ok, sounds like shuffling isn't necessary; the only benefit packing
gains me is to reduce the size of each directory in the object store;
the process I follow is to construct blobs for every revision, then just
use the sha1 values to construct an index for each commit. I never
actually look at the blobs myself, so IO access patterns aren't
relevant.
Repacking after the import is completed should undo whatever horror show
I've created in any case.
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-14 19:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 7:17 Repacking many disconnected blobs Keith Packard
2006-06-14 7:29 ` Shawn Pearce
2006-06-14 9:07 ` Johannes Schindelin
2006-06-14 12:33 ` Junio C Hamano
2006-06-14 9:37 ` Sergey Vlasov
2006-06-14 15:53 ` Linus Torvalds
2006-06-14 17:55 ` Keith Packard
2006-06-14 18:18 ` Linus Torvalds
2006-06-14 18:52 ` Linus Torvalds
2006-06-14 18:59 ` Keith Packard [this message]
2006-06-14 19:18 ` Linus Torvalds
2006-06-14 19:25 ` Nicolas Pitre
2006-06-14 21:05 ` Keith Packard
2006-06-14 21:17 ` Linus Torvalds
2006-06-14 21:20 ` Nicolas Pitre
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=1150311567.30681.28.camel@neko.keithp.com \
--to=keithp@keithp.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).