From: "Dana How" <danahow@gmail.com>
To: "Nicolas Pitre" <nico@cam.org>
Cc: "Junio C Hamano" <junkio@cox.net>,
git@vger.kernel.org, danahow@gmail.com
Subject: Re: [PATCH] always start looking up objects in the last used pack first
Date: Sat, 2 Jun 2007 07:53:35 -0700 [thread overview]
Message-ID: <56b7f5510706020753r200fe608wf55a338870f9f1ea@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.99.0705302152180.11491@xanadu.home>
On 5/30/07, Nicolas Pitre <nico@cam.org> wrote:
> Jon Smirl said:
> | Once an object reference hits a pack file it is very likely that
> | following references will hit the same pack file. So first place to
> | look for an object is the same place the previous object was found.
>
> This is indeed a good heuristic so here it is. The search always start
> with the pack where the last object lookup succeeded. If the wanted
> object is not available there then the search continues with the normal
> pack ordering.
Nice numbers for performance,
especially your later email showing this makes
split packs almost as quick as one pack.
> Note: the
> --max-pack-size to git-repack currently produces packs with old objects
> after those containing recent objects. The pack sort based on
> filesystem timestamp is therefore backward for those. This needs to be
> fixed of course, but at least it made me think about this variable for
> the test.
Yes, I was intending to submit a patch to builtin-pack-objects.c
to reverse the timestamps when split packs were created.
Haven't got around to it yet.
--
Dana L. How danahow@gmail.com +1 650 804 5991 cell
prev parent reply other threads:[~2007-06-02 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 2:48 [PATCH] always start looking up objects in the last used pack first Nicolas Pitre
2007-05-31 3:24 ` Nicolas Pitre
2007-05-31 5:02 ` Shawn O. Pearce
2007-05-31 15:39 ` Nicolas Pitre
2007-06-02 15:00 ` Dana How
2007-06-02 14:53 ` Dana How [this message]
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=56b7f5510706020753r200fe608wf55a338870f9f1ea@mail.gmail.com \
--to=danahow@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.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).