From: Avi Kivity <avi@qumranet.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Jon Smirl <jonsmirl@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org, Dana How <danahow@gmail.com>
Subject: Re: [RFC] super indexes to span multiple packfiles
Date: Wed, 30 May 2007 12:40:35 +0300 [thread overview]
Message-ID: <465D4693.5070006@qumranet.com> (raw)
In-Reply-To: <alpine.LFD.0.99.0705291227010.11491@xanadu.home>
Nicolas Pitre wrote:
>>
>> Another way to achieve that is to place objects that are accessed together
>> nearby, and issue a larger read so as to bring them into cache. I imagine
>> that placing commit objects and associated tree and blobs in history order
>> should help here (but maybe git already does that, I'm not familiar with the
>> internals).
>>
>
> GIT already does that indeed, except for commit objects which are all
> together for better performances on history traversal operations.
>
> After a fresh repack, the checkout of the latest revision should produce
> a nearly perfect linear and contigous access into the early portion of
> the same pack. Things will get more random with access to objects
> further back in history of course, but those objects are less likely to
> be accessed as often.
>
>
Thanks. Actually I should have deduced this from the speed of 'git log' ;-)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-05-30 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 7:16 [RFC] super indexes to span multiple packfiles Shawn O. Pearce
2007-05-29 16:05 ` Jon Smirl
2007-05-29 16:19 ` Nicolas Pitre
2007-05-29 16:20 ` Avi Kivity
2007-05-29 16:31 ` Nicolas Pitre
2007-05-30 9:40 ` Avi Kivity [this message]
2007-05-29 17:54 ` Geert Bosch
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=465D4693.5070006@qumranet.com \
--to=avi@qumranet.com \
--cc=danahow@gmail.com \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=nico@cam.org \
--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.