Re: [RFC PATCH 00/18] Multi-pack index (MIDX)
- Date: Wed, 10 Jan 2018 14:01:28 -0700
- From: Martin Fick <mfick@xxxxxxxxxxxxxx>
- Subject: Re: [RFC PATCH 00/18] Multi-pack index (MIDX)
On Wednesday, January 10, 2018 02:39:13 PM Derrick Stolee
> On 1/10/2018 1:25 PM, Martin Fick wrote:
> > On Sunday, January 07, 2018 01:14:41 PM Derrick Stolee
> > wrote:
> >> This RFC includes a new way to index the objects in
> >> multiple packs using one file, called the multi-pack
> >> index (MIDX).
> > ...
> >> The main goals of this RFC are:
> >> * Determine interest in this feature.
> >> * Find other use cases for the MIDX feature.
> > My interest in this feature would be to speed up fetches
> > when there is more than one large pack-file with many of
> > the same objects that are in other pack-files. What
> > does your MIDX design do when it encounters multiple
> > copies of the same object in different pack files?
> > Does it index them all, or does it keep a single copy?
> The MIDX currently keeps only one reference to each
> object. Duplicates are dropped during writing. (See the
> care taken in commit 04/18 to avoid duplicates.) Since
> midx_sha1_compare() does not use anything other than the
> OID to order the objects, there is no decision being made
> about which pack is "better". The MIDX writes the first
> copy it finds and discards the others.
This would likely speed things up then, even if the chosen
objects are suboptimal.
> It would not be difficult to include a check in
> midx_sha1_compare() to favor one packfile over another
> based on some measurement (size? mtime?). Since this
> would be a heuristic at best, I left it out of the
> current patch.
Yeah, I didn't know what heuristic to use either, I tended
to think that the bigger pack-file would be valuable because
it is more likely to share deltas with other objects in that
pack, so more easy to send them. However, that is likely
only true during clones or other large fetches when we want
most objects. During small "update" fetches, the newer
packs might be better?
I also thought that objects in alternates should be
considered less valuable for my use case, however in the
github fork use case, the alternates might be more valuable?
So yes heuristics, and I don't know what is best. Perhaps
some config options could be used to set heuristics like
this. Whatever the heuristics are, since they would be a
part of the MIDX packing process it would be easy to change.
This assumes that keeping only one copy in the index is the
right thing. The question would be, what if we need
different heuristics for different operations? Would it make
sense to have multiple MIDX files covering the same packs
then, one for fetch, one for merge...?
> > In our Gerrit instance (Gerrit uses jgit), we have
> > multiple copies of the linux kernel repos linked
> > together via the alternatives file mechanism.
> GVFS also uses alternates for sharing packfiles across
> multiple copies of the repo. The MIDX is designed to
> cover all packfiles in the same directory, but is not
> designed to cover packfiles in multiple alternates;
> currently, each alternate would need its own MIDX file.
> Does that cause issues with your setup?
No, since the other large packfiles are all in other repos
(alternates). Is there a reason the MIDX would not want to
cover the alternates? If you don't then you would seemingly
loose any benefits of the MIDX when you have alternates in
> > It would be nice if this use case could be improved with
> > MIDX. To do so, it seems that it would either require
> > that MIDX either only put "the best" version of an
> > object (i.e. pre-select which one to use), or include
> > the extra information to help make the selection
> > process of which copy to use (perhaps based on the
> > operation being performed) fast.
> I'm not sure if there is sufficient value in storing
> multiple references to the same object stored in multiple
> packfiles. There could be value in carefully deciding
> which copy is "best" during the MIDX write, but during
> read is not a good time to make such a decision. It also
> increases the size of the file to store multiple copies.
Yes, I am not sure either, it would be good to have input
from experts here.
> > This also leads me to ask, what other additional
> > information (bitmaps?) for other operations, besides
> > object location, might suddenly be valuable in an index
> > that potentially points to multiple copies of objects?
> > Would such information be appropriate in MIDX, or would
> > it be better in another index?
> For applications to bitmaps, it is probably best that we
> only include one copy of each object. Otherwise, we need
> to include extra bits in the bitmaps for those copies
> (when asking "is this object in the bitmap?").
Agreed. Would the MIDX potentially pave the way to create
> Thanks for the context with Gerrit's duplicate object
> problem. I'll try to incorporate it in to the design
> document (commit 01/18) for the v1 patch.
FYI, this is not a typical Gerrit thing, it is something
special we do in our installation.
Thanks for your thoughts,
The Qualcomm Innovation Center, Inc. is a member of Code
Aurora Forum, hosted by The Linux Foundation