1 <?xml version=
"1.0" encoding=
"UTF-8"?>
2 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.1//EN"
3 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
4 <html xmlns=
"http://www.w3.org/1999/xhtml" xml:
lang=
"en">
6 <meta http-equiv=
"Content-Type" content=
"application/xhtml+xml; charset=UTF-8" />
7 <meta name=
"generator" content=
"AsciiDoc 10.2.0" />
8 <title>Partial Clone Design Notes
</title>
9 <style type=
"text/css">
10 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
14 font-family: Georgia,serif;
18 h1, h2, h3, h4, h5, h6,
19 div.title, caption.title,
20 thead, p.table.header,
22 #author, #revnumber, #revdate, #revremark,
24 font-family: Arial,Helvetica,sans-serif;
28 margin:
1em
5%
1em
5%;
33 text-decoration: underline;
49 h1, h2, h3, h4, h5, h6 {
57 border-bottom:
2px solid silver;
77 border:
1px solid silver;
88 ul
> li { color: #aaa; }
89 ul
> li
> * { color: black; }
91 .monospaced, code, pre {
92 font-family:
"Courier New", Courier, monospace;
99 white-space: pre-wrap;
109 #revnumber, #revdate, #revremark {
114 border-top:
2px solid silver;
120 padding-bottom:
0.5em;
124 padding-bottom:
0.5em;
129 margin-bottom:
1.5em;
131 div.imageblock, div.exampleblock, div.verseblock,
132 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
133 div.admonitionblock {
135 margin-bottom:
1.5em;
137 div.admonitionblock {
139 margin-bottom:
2.0em;
144 div.content { /* Block element content. */
148 /* Block element titles. */
149 div.title, caption.title {
154 margin-bottom:
0.5em;
160 td div.title:first-child {
163 div.content div.title:first-child {
166 div.content + div.title {
170 div.sidebarblock
> div.content {
172 border:
1px solid #dddddd;
173 border-left:
4px solid #f0f0f0;
177 div.listingblock
> div.content {
178 border:
1px solid #dddddd;
179 border-left:
5px solid #f0f0f0;
184 div.quoteblock, div.verseblock {
188 border-left:
5px solid #f0f0f0;
192 div.quoteblock
> div.attribution {
197 div.verseblock
> pre.content {
198 font-family: inherit;
201 div.verseblock
> div.attribution {
205 /* DEPRECATED: Pre version
8.2.7 verse style literal block. */
206 div.verseblock + div.attribution {
210 div.admonitionblock .icon {
214 text-decoration: underline;
216 padding-right:
0.5em;
218 div.admonitionblock td.content {
220 border-left:
3px solid #dddddd;
223 div.exampleblock
> div.content {
224 border-left:
3px solid #dddddd;
228 div.imageblock div.content { padding-left:
0; }
229 span.image img { border-style: none; vertical-align: text-bottom; }
230 a.image:visited { color: white; }
234 margin-bottom:
0.8em;
247 list-style-position: outside;
250 list-style-type: decimal;
253 list-style-type: lower-alpha;
256 list-style-type: upper-alpha;
259 list-style-type: lower-roman;
262 list-style-type: upper-roman;
265 div.compact ul, div.compact ol,
266 div.compact p, div.compact p,
267 div.compact div, div.compact div {
269 margin-bottom:
0.1em;
281 margin-bottom:
0.8em;
284 padding-bottom:
15px;
286 dt.hdlist1.strong, td.hdlist1.strong {
292 padding-right:
0.8em;
298 div.hdlist.compact tr {
307 .footnote, .footnoteref {
311 span.footnote, span.footnoteref {
312 vertical-align: super;
316 margin:
20px
0 20px
0;
320 #footnotes div.footnote {
326 border-top:
1px solid silver;
335 padding-right:
0.5em;
336 padding-bottom:
0.3em;
344 #footer-badges { display: none; }
348 margin-bottom:
2.5em;
356 margin-bottom:
0.1em;
359 div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
376 span.aqua { color: aqua; }
377 span.black { color: black; }
378 span.blue { color: blue; }
379 span.fuchsia { color: fuchsia; }
380 span.gray { color: gray; }
381 span.green { color: green; }
382 span.lime { color: lime; }
383 span.maroon { color: maroon; }
384 span.navy { color: navy; }
385 span.olive { color: olive; }
386 span.purple { color: purple; }
387 span.red { color: red; }
388 span.silver { color: silver; }
389 span.teal { color: teal; }
390 span.white { color: white; }
391 span.yellow { color: yellow; }
393 span.aqua-background { background: aqua; }
394 span.black-background { background: black; }
395 span.blue-background { background: blue; }
396 span.fuchsia-background { background: fuchsia; }
397 span.gray-background { background: gray; }
398 span.green-background { background: green; }
399 span.lime-background { background: lime; }
400 span.maroon-background { background: maroon; }
401 span.navy-background { background: navy; }
402 span.olive-background { background: olive; }
403 span.purple-background { background: purple; }
404 span.red-background { background: red; }
405 span.silver-background { background: silver; }
406 span.teal-background { background: teal; }
407 span.white-background { background: white; }
408 span.yellow-background { background: yellow; }
410 span.big { font-size:
2em; }
411 span.small { font-size:
0.6em; }
413 span.underline { text-decoration: underline; }
414 span.overline { text-decoration: overline; }
415 span.line-through { text-decoration: line-through; }
417 div.unbreakable { page-break-inside: avoid; }
427 margin-bottom:
1.5em;
429 div.tableblock
> table {
430 border:
3px solid #
527bbd;
432 thead, p.table.header {
439 /* Because the table frame attribute is overridden by CSS in most browsers. */
440 div.tableblock
> table[
frame=
"void"] {
443 div.tableblock
> table[
frame=
"hsides"] {
444 border-left-style: none;
445 border-right-style: none;
447 div.tableblock
> table[
frame=
"vsides"] {
448 border-top-style: none;
449 border-bottom-style: none;
460 margin-bottom:
1.5em;
462 thead, p.tableblock.header {
473 border-color: #
527bbd;
474 border-collapse: collapse;
476 th.tableblock, td.tableblock {
480 border-color: #
527bbd;
483 table.tableblock.frame-topbot {
484 border-left-style: hidden;
485 border-right-style: hidden;
487 table.tableblock.frame-sides {
488 border-top-style: hidden;
489 border-bottom-style: hidden;
491 table.tableblock.frame-none {
492 border-style: hidden;
495 th.tableblock.halign-left, td.tableblock.halign-left {
498 th.tableblock.halign-center, td.tableblock.halign-center {
501 th.tableblock.halign-right, td.tableblock.halign-right {
505 th.tableblock.valign-top, td.tableblock.valign-top {
508 th.tableblock.valign-middle, td.tableblock.valign-middle {
509 vertical-align: middle;
511 th.tableblock.valign-bottom, td.tableblock.valign-bottom {
512 vertical-align: bottom;
523 padding-bottom:
0.5em;
524 border-top:
2px solid silver;
525 border-bottom:
2px solid silver;
530 body.manpage div.sectionbody {
535 body.manpage div#toc { display: none; }
540 <script type=
"text/javascript">
542 var asciidoc = { // Namespace.
544 /////////////////////////////////////////////////////////////////////
545 // Table Of Contents generator
546 /////////////////////////////////////////////////////////////////////
548 /* Author: Mihai Bazon, September
2002
549 * http://students.infoiasi.ro/~mishoo
551 * Table Of Content generator
554 * Feel free to use this script under the terms of the GNU General Public
555 * License, as long as you do not remove or alter this notice.
558 /* modified by Troy D. Hanson, September
2006. License: GPL */
559 /* modified by Stuart Rackham,
2006,
2009. License: GPL */
562 toc: function (toclevels) {
564 function getText(el) {
566 for (var i = el.firstChild; i != null; i = i.nextSibling) {
567 if (i.nodeType ==
3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
569 else if (i.firstChild != null)
575 function TocEntry(el, text, toclevel) {
578 this.toclevel = toclevel;
581 function tocEntries(el, toclevels) {
582 var result = new Array;
583 var re = new RegExp('[hH]([
1-'+(toclevels+
1)+'])');
584 // Function that scans the DOM tree for header elements (the DOM2
585 // nodeIterator API would be a better technique but not supported by all
587 var iterate = function (el) {
588 for (var i = el.firstChild; i != null; i = i.nextSibling) {
589 if (i.nodeType ==
1 /* Node.ELEMENT_NODE */) {
590 var mo = re.exec(i.tagName);
591 if (mo && (i.getAttribute(
"class") || i.getAttribute(
"className")) !=
"float") {
592 result[result.length] = new TocEntry(i, getText(i), mo[
1]-
1);
602 var toc = document.getElementById(
"toc");
607 // Delete existing TOC entries in case we're reloading the TOC.
608 var tocEntriesToRemove = [];
610 for (i =
0; i < toc.childNodes.length; i++) {
611 var entry = toc.childNodes[i];
612 if (entry.nodeName.toLowerCase() == 'div'
613 && entry.getAttribute(
"class")
614 && entry.getAttribute(
"class").match(/^toclevel/))
615 tocEntriesToRemove.push(entry);
617 for (i =
0; i < tocEntriesToRemove.length; i++) {
618 toc.removeChild(tocEntriesToRemove[i]);
621 // Rebuild TOC entries.
622 var entries = tocEntries(document.getElementById(
"content"), toclevels);
623 for (var i =
0; i < entries.length; ++i) {
624 var entry = entries[i];
625 if (entry.element.id ==
"")
626 entry.element.id =
"_toc_" + i;
627 var a = document.createElement(
"a");
628 a.href =
"#" + entry.element.id;
629 a.appendChild(document.createTextNode(entry.text));
630 var div = document.createElement(
"div");
632 div.className =
"toclevel" + entry.toclevel;
633 toc.appendChild(div);
635 if (entries.length ==
0)
636 toc.parentNode.removeChild(toc);
640 /////////////////////////////////////////////////////////////////////
641 // Footnotes generator
642 /////////////////////////////////////////////////////////////////////
644 /* Based on footnote generation code from:
645 * http://www.brandspankingnew.net/archive/
2005/
07/format_footnote.html
648 footnotes: function () {
649 // Delete existing footnote entries in case we're reloading the footnodes.
651 var noteholder = document.getElementById(
"footnotes");
655 var entriesToRemove = [];
656 for (i =
0; i < noteholder.childNodes.length; i++) {
657 var entry = noteholder.childNodes[i];
658 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute(
"class") ==
"footnote")
659 entriesToRemove.push(entry);
661 for (i =
0; i < entriesToRemove.length; i++) {
662 noteholder.removeChild(entriesToRemove[i]);
665 // Rebuild footnote entries.
666 var cont = document.getElementById(
"content");
667 var spans = cont.getElementsByTagName(
"span");
670 for (i=
0; i
<spans.length; i++) {
671 if (spans[i].className ==
"footnote") {
673 var note = spans[i].getAttribute(
"data-note");
675 // Use [\s\S] in place of . so multi-line matches work.
676 // Because JavaScript has no s (dotall) regex flag.
677 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[
1];
679 "[<a id='_footnoteref_" + n +
"' href='#_footnote_" + n +
680 "' title='View footnote' class='footnote'>" + n +
"</a>]";
681 spans[i].setAttribute(
"data-note", note);
683 noteholder.innerHTML +=
684 "<div class='footnote' id='_footnote_" + n +
"'>" +
685 "<a href='#_footnoteref_" + n +
"' title='Return to text'>" +
686 n +
"</a>. " + note +
"</div>";
687 var id =spans[i].getAttribute(
"id");
688 if (id != null) refs[
"#"+id] = n;
692 noteholder.parentNode.removeChild(noteholder);
694 // Process footnoterefs.
695 for (i=
0; i
<spans.length; i++) {
696 if (spans[i].className ==
"footnoteref") {
697 var href = spans[i].getElementsByTagName(
"a")[
0].getAttribute(
"href");
698 href = href.match(/#.*/)[
0]; // Because IE return full URL.
701 "[<a href='#_footnote_" + n +
702 "' title='View footnote' class='footnote'>" + n +
"</a>]";
708 install: function(toclevels) {
711 function reinstall() {
712 asciidoc.footnotes();
714 asciidoc.toc(toclevels);
718 function reinstallAndRemoveTimer() {
719 clearInterval(timerId);
723 timerId = setInterval(reinstall,
500);
724 if (document.addEventListener)
725 document.addEventListener(
"DOMContentLoaded", reinstallAndRemoveTimer, false);
727 window.onload = reinstallAndRemoveTimer;
735 <body class=
"article">
737 <h1>Partial Clone Design Notes
</h1>
738 <span id=
"revdate">2024-
04-
12</span>
742 <div class=
"sectionbody">
743 <div class=
"paragraph"><p>The
"Partial Clone" feature is a performance optimization for Git that
744 allows Git to function without having a complete copy of the repository.
745 The goal of this work is to allow Git to better handle extremely large
746 repositories.
</p></div>
747 <div class=
"paragraph"><p>During clone and fetch operations, Git downloads the complete contents
748 and history of the repository. This includes all commits, trees, and
749 blobs for the complete life of the repository. For extremely large
750 repositories, clones can take hours (or days) and consume
100+GiB of disk
752 <div class=
"paragraph"><p>Often in these repositories there are many blobs and trees that the user
753 does not need such as:
</p></div>
754 <div class=
"olist arabic"><ol class=
"arabic">
757 files outside of the user
’s work area in the tree. For example, in
758 a repository with
500K directories and
3.5M files in every commit,
759 we can avoid downloading many objects if the user only needs a
760 narrow
"cone" of the source tree.
765 large binary assets. For example, in a repository where large build
766 artifacts are checked into the tree, we can avoid downloading all
767 previous versions of these non-mergeable binary assets and only
768 download versions that are actually referenced.
772 <div class=
"paragraph"><p>Partial clone allows us to avoid downloading such unneeded objects
<strong>in
773 advance
</strong> during clone and fetch operations and thereby reduce download
774 times and disk usage. Missing objects can later be
"demand fetched"
775 if/when needed.
</p></div>
776 <div class=
"paragraph"><p>A remote that can later provide the missing objects is called a
777 promisor remote, as it promises to send the objects when
778 requested. Initially Git supported only one promisor remote, the origin
779 remote from which the user cloned and that was configured in the
780 "extensions.partialClone" config option. Later support for more than
781 one promisor remote has been implemented.
</p></div>
782 <div class=
"paragraph"><p>Use of partial clone requires that the user be online and the origin
783 remote or other promisor remotes be available for on-demand fetching
784 of missing objects. This may or may not be problematic for the user.
785 For example, if the user can stay within the pre-selected subset of
786 the source tree, they may not encounter any missing objects.
787 Alternatively, the user could try to pre-fetch various objects if they
788 know that they are going offline.
</p></div>
792 <h2 id=
"_non_goals">Non-Goals
</h2>
793 <div class=
"sectionbody">
794 <div class=
"paragraph"><p>Partial clone is a mechanism to limit the number of blobs and trees downloaded
795 <strong>within
</strong> a given range of commits
 — and is therefore independent of and not
796 intended to conflict with existing DAG-level mechanisms to limit the set of
797 requested commits (i.e. shallow clone, single branch, or fetch
<em><refspec
></em>).
</p></div>
801 <h2 id=
"_design_overview">Design Overview
</h2>
802 <div class=
"sectionbody">
803 <div class=
"paragraph"><p>Partial clone logically consists of the following parts:
</p></div>
804 <div class=
"ulist"><ul>
807 A mechanism for the client to describe unneeded or unwanted objects to
813 A mechanism for the server to omit such unwanted objects from packfiles
819 A mechanism for the client to gracefully handle missing objects (that
820 were previously omitted by the server).
825 A mechanism for the client to backfill missing objects as needed.
832 <h2 id=
"_design_details">Design Details
</h2>
833 <div class=
"sectionbody">
834 <div class=
"ulist"><ul>
837 A new pack-protocol capability
"filter" is added to the fetch-pack and
838 upload-pack negotiation.
840 <div class=
"paragraph"><p>This uses the existing capability discovery mechanism.
841 See
"filter" in
<a href=
"../gitprotocol-pack.html">gitprotocol-pack(
5)
</a>.
</p></div>
845 Clients pass a
"filter-spec" to clone and fetch which is passed to the
846 server to request filtering during packfile construction.
848 <div class=
"paragraph"><p>There are various filters available to accommodate different situations.
849 See
"--filter=<filter-spec>" in Documentation/rev-list-options.txt.
</p></div>
853 On the server pack-objects applies the requested filter-spec as it
854 creates
"filtered" packfiles for the client.
856 <div class=
"paragraph"><p>These filtered packfiles are
<strong>incomplete
</strong> in the traditional sense because
857 they may contain objects that reference objects not contained in the
858 packfile and that the client doesn
’t already have. For example, the
859 filtered packfile may contain trees or tags that reference missing blobs
860 or commits that reference missing trees.
</p></div>
864 On the client these incomplete packfiles are marked as
"promisor packfiles"
865 and treated differently by various commands.
870 On the client a repository extension is added to the local config to
871 prevent older versions of git from failing mid-operation because of
872 missing objects that they cannot handle.
873 See
"extensions.partialClone" in Documentation/technical/repository-version.txt
"
880 <h2 id="_handling_missing_objects
">Handling Missing Objects</h2>
881 <div class="sectionbody
">
882 <div class="ulist
"><ul>
885 An object may be missing due to a partial clone or fetch, or missing
886 due to repository corruption. To differentiate these cases, the
887 local repository specially indicates such filtered packfiles
888 obtained from promisor remotes as "promisor packfiles
".
890 <div class="paragraph
"><p>These promisor packfiles consist of a "<name
>.promisor
" file with
891 arbitrary contents (like the "<name
>.keep
" files), in addition to
892 their "<name
>.pack
" and "<name
>.idx
" files.</p></div>
896 The local repository considers a "promisor object
" to be an object that
897 it knows (to the best of its ability) that promisor remotes have promised
898 that they have, either because the local repository has that object in one of
899 its promisor packfiles, or because another promisor object refers to it.
901 <div class="paragraph
"><p>When Git encounters a missing object, Git can see if it is a promisor object
902 and handle it appropriately. If not, Git can report a corruption.</p></div>
903 <div class="paragraph
"><p>This means that there is no need for the client to explicitly maintain an
904 expensive-to-modify list of missing objects.[a]</p></div>
908 Since almost all Git code currently expects any referenced object to be
909 present locally and because we do not want to force every command to do
910 a dry-run first, a fallback mechanism is added to allow Git to attempt
911 to dynamically fetch missing objects from promisor remotes.
913 <div class="paragraph
"><p>When the normal object lookup fails to find an object, Git invokes
914 promisor_remote_get_direct() to try to get the object from a promisor
915 remote and then retry the object lookup. This allows objects to be
916 "faulted in
" without complicated prediction algorithms.</p></div>
917 <div class="paragraph
"><p>For efficiency reasons, no check as to whether the missing object is
918 actually a promisor object is performed.</p></div>
919 <div class="paragraph
"><p>Dynamic object fetching tends to be slow as objects are fetched one at
924 <code>checkout</code> (and any other command using <code>unpack-trees</code>) has been taught
925 to bulk pre-fetch all required missing blobs in a single batch.
930 <code>rev-list</code> has been taught to print missing objects.
932 <div class="paragraph
"><p>This can be used by other commands to bulk prefetch objects.
933 For example, a "git log -p A..B
" may internally want to first do
934 something like "git rev-list --objects --quiet --missing=print A..B
"
935 and prefetch those objects in bulk.</p></div>
939 <code>fsck</code> has been updated to be fully aware of promisor objects.
944 <code>repack</code> in GC has been updated to not touch promisor packfiles at all,
945 and to only repack other objects.
950 The global variable "fetch_if_missing
" is used to control whether an
951 object lookup will attempt to dynamically fetch a missing object or
954 <div class="paragraph
"><p>We are not happy with this global variable and would like to remove it,
955 but that requires significant refactoring of the object code to pass an
956 additional flag.</p></div>
962 <h2 id="_fetching_missing_objects
">Fetching Missing Objects</h2>
963 <div class="sectionbody
">
964 <div class="ulist
"><ul>
967 Fetching of objects is done by invoking a "git fetch
" subprocess.
972 The local repository sends a request with the hashes of all requested
973 objects, and does not perform any packfile negotiation.
974 It then receives a packfile.
979 Because we are reusing the existing fetch mechanism, fetching
980 currently fetches all objects referred to by the requested objects, even
981 though they are not necessary.
986 Fetching with <code>--refetch</code> will request a complete new filtered packfile from
987 the remote, which can be used to change a filter without needing to
988 dynamically fetch missing objects.
995 <h2 id="_using_many_promisor_remotes
">Using many promisor remotes</h2>
996 <div class="sectionbody
">
997 <div class="paragraph
"><p>Many promisor remotes can be configured and used.</p></div>
998 <div class="paragraph
"><p>This allows for example a user to have multiple geographically-close
999 cache servers for fetching missing blobs while continuing to do
1000 filtered <code>git-fetch</code> commands from the central server.</p></div>
1001 <div class="paragraph
"><p>When fetching objects, promisor remotes are tried one after the other
1002 until all the objects have been fetched.</p></div>
1003 <div class="paragraph
"><p>Remotes that are considered "promisor
" remotes are those specified by
1004 the following configuration variables:</p></div>
1005 <div class="ulist
"><ul>
1008 <code>extensions.partialClone = <name></code>
1013 <code>remote.<name>.promisor = true</code>
1018 <code>remote.<name>.partialCloneFilter = ...</code>
1022 <div class="paragraph
"><p>Only one promisor remote can be configured using the
1023 <code>extensions.partialClone</code> config variable. This promisor remote will
1024 be the last one tried when fetching objects.</p></div>
1025 <div class="paragraph
"><p>We decided to make it the last one we try, because it is likely that
1026 someone using many promisor remotes is doing so because the other
1027 promisor remotes are better for some reason (maybe they are closer or
1028 faster for some kind of objects) than the origin, and the origin is
1029 likely to be the remote specified by extensions.partialClone.</p></div>
1030 <div class="paragraph
"><p>This justification is not very strong, but one choice had to be made,
1031 and anyway the long term plan should be to make the order somehow
1032 fully configurable.</p></div>
1033 <div class="paragraph
"><p>For now though the other promisor remotes will be tried in the order
1034 they appear in the config file.</p></div>
1038 <h2 id="_current_limitations
">Current Limitations</h2>
1039 <div class="sectionbody
">
1040 <div class="ulist
"><ul>
1043 It is not possible to specify the order in which the promisor
1044 remotes are tried in other ways than the order in which they appear
1047 <div class="paragraph
"><p>It is also not possible to specify an order to be used when fetching
1048 from one remote and a different order when fetching from another
1053 It is not possible to push only specific objects to a promisor
1056 <div class="paragraph
"><p>It is not possible to push at the same time to multiple promisor
1057 remote in a specific order.</p></div>
1061 Dynamic object fetching will only ask promisor remotes for missing
1062 objects. We assume that promisor remotes have a complete view of the
1063 repository and can satisfy all such requests.
1068 Repack essentially treats promisor and non-promisor packfiles as 2
1069 distinct partitions and does not mix them.
1074 Dynamic object fetching invokes fetch-pack once <strong>for each item</strong>
1075 because most algorithms stumble upon a missing object and need to have
1076 it resolved before continuing their work. This may incur significant
1077 overhead — and multiple authentication requests — if many objects are
1083 Dynamic object fetching currently uses the existing pack protocol V0
1084 which means that each object is requested via fetch-pack. The server
1085 will send a full set of info/refs when the connection is established.
1086 If there are a large number of refs, this may incur significant overhead.
1093 <h2 id="_future_work
">Future Work</h2>
1094 <div class="sectionbody
">
1095 <div class="ulist
"><ul>
1098 Improve the way to specify the order in which promisor remotes are
1101 <div class="paragraph
"><p>For example this could allow specifying explicitly something like:
1102 "When fetching from this remote, I want to use these promisor remotes
1103 in this order, though, when pushing or fetching to that remote, I want
1104 to use those promisor remotes in that order.
"</p></div>
1108 Allow pushing to promisor remotes.
1110 <div class="paragraph
"><p>The user might want to work in a triangular work flow with multiple
1111 promisor remotes that each have an incomplete view of the repository.</p></div>
1115 Allow non-pathname-based filters to make use of packfile bitmaps (when
1116 present). This was just an omission during the initial implementation.
1121 Investigate use of a long-running process to dynamically fetch a series
1122 of objects, such as proposed in [5,6] to reduce process startup and
1125 <div class="paragraph
"><p>It would be nice if pack protocol V2 could allow that long-running
1126 process to make a series of requests over a single long-running
1127 connection.</p></div>
1131 Investigate pack protocol V2 to avoid the info/refs broadcast on
1132 each connection with the server to dynamically fetch missing objects.
1137 Investigate the need to handle loose promisor objects.
1139 <div class="paragraph
"><p>Objects in promisor packfiles are allowed to reference missing objects
1140 that can be dynamically fetched from the server. An assumption was
1141 made that loose objects are only created locally and therefore should
1142 not reference a missing object. We may need to revisit that assumption
1143 if, for example, we dynamically fetch a missing tree and store it as a
1144 loose object rather than a single object packfile.</p></div>
1145 <div class="paragraph
"><p>This does not necessarily mean we need to mark loose objects as promisor;
1146 it may be sufficient to relax the object lookup or is-promisor functions.</p></div>
1152 <h2 id="_non_tasks
">Non-Tasks</h2>
1153 <div class="sectionbody
">
1154 <div class="ulist
"><ul>
1157 Every time the subject of "demand loading blobs
" comes up it seems
1158 that someone suggests that the server be allowed to "guess
" and send
1159 additional objects that may be related to the requested objects.
1161 <div class="paragraph
"><p>No work has gone into actually doing that; we’re just documenting that
1162 it is a common suggestion. We’re not sure how it would work and have
1163 no plans to work on it.</p></div>
1164 <div class="paragraph
"><p>It is valid for the server to send more objects than requested (even
1165 for a dynamic object fetch), but we are not building on that.</p></div>
1171 <h2 id="_footnotes
">Footnotes</h2>
1172 <div class="sectionbody
">
1173 <div class="paragraph
"><p>[a] expensive-to-modify list of missing objects: Earlier in the design of
1174 partial clone we discussed the need for a single list of missing objects.
1175 This would essentially be a sorted linear list of OIDs that were
1176 omitted by the server during a clone or subsequent fetches.</p></div>
1177 <div class="paragraph
"><p>This file would need to be loaded into memory on every object lookup.
1178 It would need to be read, updated, and re-written (like the .git/index)
1179 on every explicit "git fetch
" command <strong>and</strong> on any dynamic object fetch.</p></div>
1180 <div class="paragraph
"><p>The cost to read, update, and write this file could add significant
1181 overhead to every command if there are many missing objects. For example,
1182 if there are 100M missing blobs, this file would be at least 2GiB on disk.</p></div>
1183 <div class="paragraph
"><p>With the "promisor
" concept, we <strong>infer</strong> a missing object based upon the
1184 type of packfile that references it.</p></div>
1188 <h2 id="_related_links
">Related Links</h2>
1189 <div class="sectionbody
">
1190 <div class="paragraph
"><p>[0] <a href="https://crbug.com/git/
2">https://crbug.com/git/2</a>
1191 Bug#2: Partial Clone</p></div>
1192 <div class="paragraph
"><p>[1] <a href="https://lore.kernel.org/git/
20170113155253.1644-
1-benpeart@microsoft.com/
">https://lore.kernel.org/git/20170113155253.1644-1-benpeart@microsoft.com/</a><br />
1193 Subject: [RFC] Add support for downloading blobs on demand<br />
1194 Date: Fri, 13 Jan 2017 10:52:53 -0500</p></div>
1195 <div class="paragraph
"><p>[2] <a href="https://lore.kernel.org/git/cover
.1506714999.git.jonathantanmy@google.com/
">https://lore.kernel.org/git/cover.1506714999.git.jonathantanmy@google.com/</a><br />
1196 Subject: [PATCH 00/18] Partial clone (from clone to lazy fetch in 18 patches)<br />
1197 Date: Fri, 29 Sep 2017 13:11:36 -0700</p></div>
1198 <div class="paragraph
"><p>[3] <a href="https://lore.kernel.org/git/
20170426221346.25337-
1-jonathantanmy@google.com/
">https://lore.kernel.org/git/20170426221346.25337-1-jonathantanmy@google.com/</a><br />
1199 Subject: Proposal for missing blob support in Git repos<br />
1200 Date: Wed, 26 Apr 2017 15:13:46 -0700</p></div>
1201 <div class="paragraph
"><p>[4] <a href="https://lore.kernel.org/git/
1488999039-
37631-
1-git-send-email-git@jeffhostetler.com/
">https://lore.kernel.org/git/1488999039-37631-1-git-send-email-git@jeffhostetler.com/</a><br />
1202 Subject: [PATCH 00/10] RFC Partial Clone and Fetch<br />
1203 Date: Wed, 8 Mar 2017 18:50:29 +0000</p></div>
1204 <div class="paragraph
"><p>[5] <a href="https://lore.kernel.org/git/
20170505152802.6724-
1-benpeart@microsoft.com/
">https://lore.kernel.org/git/20170505152802.6724-1-benpeart@microsoft.com/</a><br />
1205 Subject: [PATCH v7 00/10] refactor the filter process code into a reusable module<br />
1206 Date: Fri, 5 May 2017 11:27:52 -0400</p></div>
1207 <div class="paragraph
"><p>[6] <a href="https://lore.kernel.org/git/
20170714132651.170708-
1-benpeart@microsoft.com/
">https://lore.kernel.org/git/20170714132651.170708-1-benpeart@microsoft.com/</a><br />
1208 Subject: [RFC/PATCH v2 0/1] Add support for downloading blobs on demand<br />
1209 Date: Fri, 14 Jul 2017 09:26:50 -0400</p></div>
1213 <div id="footnotes
"><hr /></div>
1215 <div id="footer-text
">
1217 2023-10-23 14:43:46 PDT