From: Jeff King <hidden> Date: 2017-01-24 00:37:36
As I've mentioned before, I have some alternates repositories with
absurd numbers of refs, most of which are duplicates of each other[1].
There are a couple of problems I've seen:
1. the way that for_each_alternate_ref() works has very high peak memory
usage for this case
2. the way that receive-pack de-duplicates the refs has high peak memory
usage
3. we access the alternate refs twice in fetch-pack
This fixes all three, along with a few other minor bugfixes, cleanups,
and optimizations. I've tried to order the series to keep bugfixes and
less-contentious changes near the front.
Just to give some numbers, on my worst-case repository (see [1]), this
drops peak RSS for "git clone --reference" from over 25GB to about 40MB.
Sort of, anyway. You still pay a big CPU and RSS cost on the process in
the alternates repo that accesses packed-refs, but the 25GB came on top
of that. So this is a first pass at the low-hanging fruit.
I'll be the first to admit that this setup is insane. And some of the
optimizations are tradeoffs that help particularly the case where your
refs aren't unique. But for the most part should help _every_ case. And
in the cases where your refs are unique, either you don't have many (so
the tradeoffs are OK) or you have so many that you are pretty much
screwed no matter what (if your fetch is looking at 30 million unique
ref tips, the object storage is your problem, not looking at the refs).
A brief overview of the patches:
[01/12]: for_each_alternate_ref: handle failure from real_pathdup()
[02/12]: for_each_alternate_ref: stop trimming trailing slashes
[03/12]: for_each_alternate_ref: use strbuf for path allocation
Bugfixes and cleanups (the first one is actually a recent-ish
regression).
[04/12]: for_each_alternate_ref: pass name/oid instead of ref struct
[05/12]: for_each_alternate_ref: replace transport code with for-each-ref
[06/12]: clone: disable save_commit_buffer
This gives the 25GB->40MB benefit. There are a bunch of caveats in
patch 05, but I _think_ it's the right direction for the reasons I
outlined there.
[07/12]: fetch-pack: cache results of for_each_alternate_ref
Just running for-each-ref in the giant alternates repo is about a
minute of CPU, plus 10GB heap, and fetch-pack wants to do it twice.
This drops it to once.
[08/12]: add oidset API
[09/12]: receive-pack: use oidset to de-duplicate .have lines
These give another ~12GB RSS improvement when receive-pack looks at
the alternates in my worst-case repo.
This is less tested than the earlier ones, as we've disabled
receive-pack looking at alternates in production (see [1] below).
I just did them for completeness upstream.
[10/12]: receive-pack: fix misleading namespace/.have comment
[11/12]: receive-pack: treat namespace .have lines like alternates
[12/12]: receive-pack: avoid duplicates between our refs and alternates
These are optimizations to avoid more duplicate .have lines, and
should benefit even non-insane cases. As with 8-12, not as well
tested by me.
Makefile | 1 +
builtin/clone.c | 1 +
builtin/receive-pack.c | 41 +++++++++++++++-------------
fetch-pack.c | 48 ++++++++++++++++++++++++++++-----
object.h | 2 +-
oidset.c | 49 ++++++++++++++++++++++++++++++++++
oidset.h | 45 +++++++++++++++++++++++++++++++
t/t5400-send-pack.sh | 38 ++++++++++++++++++++++++++
transport.c | 72 +++++++++++++++++++++++++++++++++++---------------
transport.h | 2 +-
10 files changed, 250 insertions(+), 49 deletions(-)
create mode 100644 oidset.c
create mode 100644 oidset.h
-Peff
[1] Background, if you care:
I've mentioned before that GitHub's repository storage uses a
fork-network layout. Each user gets their own "fork" repository, and
it points to "network.git" as shared storage. The network.git
repository has a ref for each fork that is updated periodically via
"git fetch".
So the network.git repo contains O(nr_forks * nr_refs_in_fork) refs.
Quite a few of these point to the same tip sha1s, as each fork has
the same tags. One of the most pathological cases is a popular
public repo that has ~44K tags in it. The network repo has ~80
million refs, of which ~60K are unique. You can imagine that it
takes some time to access the refs. Basically anything that loads
the network.git packed-refs file takes an extra minute of CPU and
needs ~10G RSS to store the internal cache of `packed-refs`.
Most operations don't care about this; they work on the fork repo,
and never look at the network refs. But we _do_ sometimes peek at
alternate refs from receive-pack and fetch-pack to tell the other
side about tips we have.
These optimizations backfire completely in such a setting. Besides
the CPU and memory spikes on the server, even just the unique refs
add over 3MB to the ref advertisement. So for the time being, we've
disabled them. I have patches that add a receive.advertiseAlternates
config option, if anybody is interested.
So why do I care? There is one exception: when we are cloning a
fork, we turn on the fetch-pack side of the optimizations. This is
worth it for a large repository, as it saves us having to transfer
any objects at all (and therefore not process them with index-pack,
which is expensive).
This series is also a first step towards other optimizations, like
asking for just the alternate refs from _one_ of the forks. I hope
one day to turn alternates optimizations back on everywhere.
From: Jeff King <hidden> Date: 2017-01-24 00:38:33
In older versions of git, if real_path() failed to resolve
the alternate object store path, we would die() with an
error. However, since 4ac9006f8 (real_path: have callers use
real_pathdup and strbuf_realpath, 2016-12-12) we use the
real_pathdup() function, which may return NULL. Since we
don't check the return value, we can segfault.
This is hard to trigger in practice, since we check that the
path is accessible before creating the alternate_object_database
struct. But it could be removed racily, or we could see a
transient filesystem error.
We could restore the original behavior by switching back to
xstrdup(real_path()). However, dying is probably not the
best option here. This whole function is best-effort
already; there might not even be a repository around the
shared objects at all. And if the alternate store has gone
away, there are no objects to show.
So let's just quietly return, as we would if we failed to
open "refs/", or if upload-pack failed to start, etc.
Signed-off-by: Jeff King <redacted>
---
transport.c | 2 ++
1 file changed, 2 insertions(+)
From: Jeff King <hidden> Date: 2017-01-24 00:39:52
The real_pathdup() function will have removed extra slashes
for us already (on top of the normalize_path() done when we
created the alternate_object_database struct in the first
place).
Incidentally, this also fixes the case where the path is
just "/", which would read off the start of the array.
That doesn't seem possible to trigger in practice, though,
as link_alt_odb_entry() blindly eats trailing slashes,
including a bare "/".
Signed-off-by: Jeff King <redacted>
---
I think the "/" thing in link_alt_odb_entry() is buggy, and it's an easy
one-liner fix. But I notice some of the rest of the code isn't ready to
handle "/" (mostly it just duplicates "/" when appending to the path),
so I left it for now (and I doubt anybody cares anyway).
transport.c | 2 --
1 file changed, 2 deletions(-)
@@ -1219,8 +1219,6 @@ static int refs_from_alternate_cb(struct alternate_object_database *e,return0;len=strlen(other);-while(other[len-1]=='/')-other[--len]='\0';if(len<8||memcmp(other+len-8,"/objects",8))gotoout;/* Is this a git repository with refs? */
From: Jeff King <hidden> Date: 2017-01-24 00:40:44
We have a string with ".../objects" pointing to the
alternate object store, and overwrite bits of it to look at
other paths in the (potential) git repository holding it.
This works because the only path we care about is "refs",
which is shorter than "objects".
Using a strbuf to hold the path lets us get rid of some
magic numbers, and makes it more obvious that the memory
operations are safe.
Signed-off-by: Jeff King <redacted>
---
I had thought I was going to need to generate more paths in the
alternate repo, but I ended up not needing to. So this was originally
done to make that easier, but I think it stands on its own as a cleanup.
transport.c | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
@@ -1207,34 +1207,34 @@ struct alternate_refs_data {staticintrefs_from_alternate_cb(structalternate_object_database*e,void*data){-char*other;-size_tlen;+structstrbufpath=STRBUF_INIT;+size_tbase_len;structremote*remote;structtransport*transport;conststructref*extra;structalternate_refs_data*cb=data;-other=real_pathdup(e->path);-if(!other)-return0;-len=strlen(other);--if(len<8||memcmp(other+len-8,"/objects",8))+if(!strbuf_realpath(&path,e->path,0))+gotoout;+if(!strbuf_strip_suffix(&path,"/objects"))gotoout;+base_len=path.len;+/* Is this a git repository with refs? */-memcpy(other+len-8,"/refs",6);-if(!is_directory(other))+strbuf_addstr(&path,"/refs");+if(!is_directory(path.buf))gotoout;-other[len-8]='\0';-remote=remote_get(other);-transport=transport_get(remote,other);+strbuf_setlen(&path,base_len);++remote=remote_get(path.buf);+transport=transport_get(remote,path.buf);for(extra=transport_get_remote_refs(transport);extra;extra=extra->next)cb->fn(extra,cb->data);transport_disconnect(transport);out:-free(other);+strbuf_release(&path);return0;}
From: Jeff King <hidden> Date: 2017-01-24 00:41:03
Breaking down the fields in the interface makes it easier to
change the backend of for_each_alternate_ref to something
that doesn't use "struct ref" internally.
The only field that callers actually look at is the oid,
anyway. The refname is kept in the interface as a plausible
thing for future code to want.
Signed-off-by: Jeff King <redacted>
---
builtin/receive-pack.c | 6 ++++--
fetch-pack.c | 12 ++++++++----
transport.c | 2 +-
transport.h | 2 +-
4 files changed, 14 insertions(+), 8 deletions(-)
From: Jeff King <hidden> Date: 2017-01-24 00:44:21
The current method for getting the refs from an alternate is
to run upload-pack in the alternate and parse its output
using the normal transport code. This works and is
reasonably short, but it has a very bad memory footprint
when there are a lot of refs in the alternate. There are two
problems:
1. It reads in all of the refs before passing any back to
us. Which means that our peak memory usage has to store
every ref (including duplicates for peeled variants),
even if our callback could determine that some are not
interesting (e.g., because they point to the same sha1
as another ref).
2. It allocates a "struct ref" for each one. Among other
things, this contains 3 separate 20-byte oids, along
with the name and various pointers. That can add up,
especially if the callback is only interested in the
sha1 (which it can store in a sha1_array as just 20
bytes).
On a particularly pathological case, where the alternate had
over 80 million refs pointing to only around 60,000 unique
objects, the peak heap usage of "git clone --reference" grew
to over 25GB.
This patch instead calls git-for-each-ref in the alternate
repository, and passes each line to the callback as we read
it. That drops the peak heap of the same command to 50MB.
I considered and rejected a few alternatives.
We could read all of the refs in the alternate using our own
ref code, just as we do with submodules. However, as memory
footprint is one of the concerns here, we want to avoid
loading those refs into our own memory as a whole.
It's possible that this will be a better technique in the
future when the ref code can more easily iterate without
loading all of packed-refs into memory.
Another option is to keep calling upload-pack, and just
parse its output ourselves in a streaming fashion. Besides
for-each-ref being simpler (we get to define the format
ourselves, and don't have to deal with speaking the git
protocol), it's more flexible for possible future changes.
For instance, it might be useful for the caller to be able
to limit the set of "interesting" alternate refs. The
motivating example is one where many "forks" of a particular
repository share object storage, and the shared storage has
refs for each fork (which is why so many of the refs are
duplicates; each fork has the same tags). A plausible
future optimization would be to ask for the alternate refs
for just _one_ fork (if you had some out-of-band way of
knowing which was the most interesting or important for the
current operation).
Similarly, no callbacks actually care about the symref value
of alternate refs, and as before, this patch ignores them
entirely. However, if we wanted to add them, for-each-ref's
"%(symref)" is going to be more flexible than upload-pack,
because the latter only handles the HEAD symref due to
historical constraints.
There is one potential downside, though: unlike upload-pack,
our for-each-ref command doesn't report the peeled value of
refs. The existing code calls the alternate_ref_fn callback
twice for tags: once for the tag, and once for the peeled
value with the refname set to "ref^{}".
For the callers in fetch-pack, this doesn't matter at all.
We immediately peel each tag down to a commit either way (so
there's a slight improvement, as do not bother passing the
redundant data over the pipe). For the caller in
receive-pack, it means we will not advertise the peeled
values of tags in our alternate. However, we also don't
advertise peeled values for our _own_ tags, so this is
actually making things more consistent.
It's unclear whether receive-pack advertising peeled values
is a win or not. On one hand, giving more information to the
other side may let it omit some objects from the push. On
the other hand, for tags which both sides have, they simply
bloat the advertisement. The upload-pack advertisement of
git.git is about 30% larger than the receive-pack
advertisement due to its peeled information.
This patch omits the peeled information from
for_each_alternate_ref entirely, and leaves it up to the
caller whether they want to dig up the information.
Signed-off-by: Jeff King <redacted>
---
I also tried adding "%(*objectname)" to for-each-ref to just
grab the peeled information, but the peel implementation in
ref-filter is _really_ slow. It doesn't use the packed-ref
peel information, and it doesn't recognize duplicates (so in
the 80 million case, it really parses 80 million tags).
transport.c | 48 ++++++++++++++++++++++++++++++++++++++----------
1 file changed, 38 insertions(+), 10 deletions(-)
From: Jeff King <hidden> Date: 2017-01-24 00:45:07
Normally git caches the raw commit object contents in
"struct commit". This makes it fast to run parse_commit()
followed by a pretty-print operation.
For commands which don't actually pretty-print the commits,
the caching is wasteful (and may use quite a lot of memory
if git accesses a large number of commits).
For fetching operations like clone, we already disable
save_commit_buffer in everything_local(), where we may
traverse. But clone also parses commits before it even gets
there; it looks at commits reachable from its refs, and from
alternate refs.
In one real-world case with a large number of tags, this
cut about 10MB off of clone's heap usage. Not spectacular,
but there's really no downside.
Signed-off-by: Jeff King <redacted>
---
builtin/clone.c | 1 +
1 file changed, 1 insertion(+)
From: Jeff King <hidden> Date: 2017-01-24 00:47:24
We may run for_each_alternate_ref() twice, once in
find_common() and once in everything_local(). This operation
can be expensive, because it involves running a sub-process
which must freshly load all of the alternate's refs from
disk.
Let's cache and reuse the results between the two calls. We
can make some optimizations based on the particular use
pattern in fetch-pack to keep our memory usage down.
The first is that we only care about the sha1s, not the refs
themselves. So it's OK to store only the sha1s, and to
suppress duplicates. The natural fit would therefore be a
sha1_array.
However, sha1_array's de-duplication happens only after it
has read and sorted all entries. It still stores each
duplicate. For an alternate with a large number of refs
pointing to the same commits, this is a needless expense.
Instead, we'd prefer to eliminate duplicates before putting
them in the cache, which implies using a hash. We can
further note that fetch-pack will call parse_object() on
each alternate sha1. We can therefore keep our cache as a
set of pointers to "struct object". That gives us a place to
put our "already seen" bit with an optimized hash lookup.
And as a bonus, the object stores the sha1 for us, so
pointer-to-object is all we need.
There are two extra optimizations I didn't do here:
- we actually store an array of pointer-to-object.
Technically we could just walk the obj_hash table
looking for entries with the ALTERNATE flag set (because
our use case doesn't care about the order here).
But that hash table may be mostly composed of
non-ALTERNATE entries, so we'd waste time walking over
them. So it would be a slight win in memory use, but a
loss in CPU.
- the items we pull out of the cache are actual "struct
object"s, but then we feed "obj->sha1" to our
sub-functions, which promptly call parse_object().
This second parse is cheap, because it starts with
lookup_object() and will bail immediately when it sees
we've already parsed the object. We could save the extra
hash lookup, but it would involve refactoring the
functions we call. It may or may not be worth the
trouble.
Signed-off-by: Jeff King <redacted>
---
fetch-pack.c | 52 ++++++++++++++++++++++++++++++++++++++++++----------
object.h | 2 +-
2 files changed, 43 insertions(+), 11 deletions(-)
From: Jeff King <hidden> Date: 2017-01-24 00:47:40
This is similar to many of our uses of sha1-array, but it
overcomes one limitation of a sha1-array: when you are
de-duplicating a large input with relatively few unique
entries, sha1-array uses 20 bytes per non-unique entry.
Whereas this set will use memory linear in the number of
unique entries (albeit a few more than 20 bytes due to
hashmap overhead).
Signed-off-by: Jeff King <redacted>
---
This may be overkill. You can get roughly the same thing by making
actual object structs via lookup_unknown_object(). But see the next
patch for some comments on that.
Makefile | 1 +
oidset.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
oidset.h | 45 +++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 95 insertions(+)
create mode 100644 oidset.c
create mode 100644 oidset.h
From: Ramsay Jones <hidden> Date: 2017-01-24 20:26:48
On 24/01/17 00:46, Jeff King wrote:
quoted hunk
This is similar to many of our uses of sha1-array, but it
overcomes one limitation of a sha1-array: when you are
de-duplicating a large input with relatively few unique
entries, sha1-array uses 20 bytes per non-unique entry.
Whereas this set will use memory linear in the number of
unique entries (albeit a few more than 20 bytes due to
hashmap overhead).
Signed-off-by: Jeff King <redacted>
---
This may be overkill. You can get roughly the same thing by making
actual object structs via lookup_unknown_object(). But see the next
patch for some comments on that.
Makefile | 1 +
oidset.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
oidset.h | 45 +++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 95 insertions(+)
create mode 100644 oidset.c
create mode 100644 oidset.h
From: Jeff King <hidden> Date: 2017-01-24 00:47:55
The comment claims that we handle alternate ".have" lines
through this function, but that hasn't been the case since
85f251045 (write_head_info(): handle "extra refs" locally,
2012-01-06).
Signed-off-by: Jeff King <redacted>
---
builtin/receive-pack.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
From: Jeff King <hidden> Date: 2017-01-24 00:47:58
If you have an alternate object store with a very large
number of refs, the peak memory usage of the sha1_array can
grow high, even if most of them are duplicates that end up
not being printed at all.
The similar for_each_alternate_ref() code-paths in
fetch-pack solve this by using flags in "struct object" to
de-duplicate (and so are relying on obj_hash at the core).
But we don't have a "struct object" at all in this case. We
could call lookup_unknown_object() to get one, but if our
goal is reducing memory footprint, it's not great:
- an unknown object is as large as the largest object type
(a commit), which is bigger than an oidset entry
- we can free the memory after our ref advertisement, but
"struct object" entries persist forever (and the
receive-pack may hang around for a long time, as the
bottleneck is often client upload bandwidth).
So let's use an oidset. Note that unlike a sha1-array it
doesn't sort the output as a side effect. However, our
output is at least stable, because for_each_alternate_ref()
will give us the sha1s in ref-sorted order.
In one particularly pathological case with an alternate that
has 60,000 unique refs out of 80 million total, this reduced
the peak heap usage of "git receive-pack . </dev/null" from
13GB to 14MB.
Signed-off-by: Jeff King <redacted>
---
builtin/receive-pack.c | 26 ++++++++++++--------------
1 file changed, 12 insertions(+), 14 deletions(-)
From: Jeff King <hidden> Date: 2017-01-24 00:48:29
We de-duplicate ".have" refs among themselves, but never
check if they are duplicates of our local refs. It's not
unreasonable that they would be if we are a "--shared" or
"--reference" clone of a similar repository; we'd have all
the same tags.
We can handle this by inserting our local refs into the
oidset, but obviously not suppressing duplicates (since the
refnames are important).
Note that this also switches the order in which we advertise
refs, processing ours first and then any alternates. The
order shouldn't matter (and arguably showing our refs first
makes more sense).
Signed-off-by: Jeff King <redacted>
---
builtin/receive-pack.c | 4 +++-
t/t5400-send-pack.sh | 38 ++++++++++++++++++++++++++++++++++++++
2 files changed, 41 insertions(+), 1 deletion(-)
@@ -255,4 +255,42 @@ test_expect_success 'deny pushing to delete current branch' ')'+extract_ref_advertisement(){+perl-lne'+# \\ is there to skip capabilities after \0+/push<([^\\]+)/ornext;+exit0if$1eq"0000";+print$1;+'+}++test_expect_success'receive-pack de-dupes .have lines''+gitinitshared&&+git-Csharedcommit--allow-empty-mboth&&+gitclone-ssharedfork&&+(+cdshared&&+gitcheckout-bonly-shared&&+gitcommit--allow-empty-monly-shared&&+gitupdate-refrefs/heads/fooHEAD+)&&++# Notable things in this expectation:+# - local refs are not de-duped+# - .have does not duplicate locals+# - .have does not duplicate itself+local=$(git-Cforkrev-parseHEAD)&&+shared=$(git-Csharedrev-parseonly-shared)&&+cat>expect<<-EOF&&+$localrefs/heads/master+$localrefs/remotes/origin/HEAD+$localrefs/remotes/origin/master+$shared.have+EOF++GIT_TRACE_PACKET=$(pwd)/tracegitpushforkHEAD:foo&&+extract_ref_advertisement<trace>refs&&+test_cmpexpectrefs+'+ test_done
From: Jeff King <hidden> Date: 2017-01-24 00:48:32
Namely, de-duplicate them. We use the same set as the
alternates, since we call them both ".have" (i.e., there is
no value in showing one versus the other).
Signed-off-by: Jeff King <redacted>
---
builtin/receive-pack.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
From: Brandon Williams <hidden> Date: 2017-01-24 01:33:48
On 01/23, Jeff King wrote:
A brief overview of the patches:
[01/12]: for_each_alternate_ref: handle failure from real_pathdup()
[02/12]: for_each_alternate_ref: stop trimming trailing slashes
[03/12]: for_each_alternate_ref: use strbuf for path allocation
Bugfixes and cleanups (the first one is actually a recent-ish
regression).
Which is most likely my fault, Sorry! :)
I think the old behavior was to die and not return NULL.
--
Brandon Williams
From: Jeff King <hidden> Date: 2017-01-24 02:12:26
On Mon, Jan 23, 2017 at 05:33:41PM -0800, Brandon Williams wrote:
On 01/23, Jeff King wrote:
quoted
A brief overview of the patches:
[01/12]: for_each_alternate_ref: handle failure from real_pathdup()
[02/12]: for_each_alternate_ref: stop trimming trailing slashes
[03/12]: for_each_alternate_ref: use strbuf for path allocation
Bugfixes and cleanups (the first one is actually a recent-ish
regression).
Which is most likely my fault, Sorry! :)
I think the old behavior was to die and not return NULL.
Yes, it is. :)
But I think it's probably pretty hard to trigger in practice. And on the
plus side, I think the new behavior after my patch is much more sensible
than even the original.
-Peff
From: Jeff King <hidden> Date: 2017-02-08 20:59:07
This is a minor re-roll of the patches from:
http://public-inbox.org/git/20170124003729.j4ygjcgypdq7hceg@sigill.intra.peff.net/
(which got some review, but I don't think was picked up for even 'pu').
I won't repeat the numbers and background from that message, but the
gist of it is that this reduces memory usage significantly when your
alternate has a lot of refs in it.
This version makes two minor changes:
- it drops the save_commit_buffer patch to clone; it's redundant with
what fetch_pack() is doing internally, and I wasn't able to measure
any improvement
- it adds a missing "static" to an internal function
The only other possible change from the review would be sorting the
expected output in the test of the final script. I'm on the fence
whether it is a feature that we expect a particular ordering. It's not
set in stone ,but it _is_ deterministic, and if we change the order, it
might be worth somebody actually noticing.
[01/11]: for_each_alternate_ref: handle failure from real_pathdup()
[02/11]: for_each_alternate_ref: stop trimming trailing slashes
[03/11]: for_each_alternate_ref: use strbuf for path allocation
[04/11]: for_each_alternate_ref: pass name/oid instead of ref struct
[05/11]: for_each_alternate_ref: replace transport code with for-each-ref
[06/11]: fetch-pack: cache results of for_each_alternate_ref
[07/11]: add oidset API
[08/11]: receive-pack: use oidset to de-duplicate .have lines
[09/11]: receive-pack: fix misleading namespace/.have comment
[10/11]: receive-pack: treat namespace .have lines like alternates
[11/11]: receive-pack: avoid duplicates between our refs and alternates
Makefile | 1 +
builtin/receive-pack.c | 41 +++++++++++++++-------------
fetch-pack.c | 48 ++++++++++++++++++++++++++++-----
object.h | 2 +-
oidset.c | 49 ++++++++++++++++++++++++++++++++++
oidset.h | 45 +++++++++++++++++++++++++++++++
t/t5400-send-pack.sh | 38 ++++++++++++++++++++++++++
transport.c | 72 +++++++++++++++++++++++++++++++++++---------------
transport.h | 2 +-
9 files changed, 249 insertions(+), 49 deletions(-)
create mode 100644 oidset.c
create mode 100644 oidset.h
From: Jeff King <hidden> Date: 2017-02-08 20:59:32
In older versions of git, if real_path() failed to resolve
the alternate object store path, we would die() with an
error. However, since 4ac9006f8 (real_path: have callers use
real_pathdup and strbuf_realpath, 2016-12-12) we use the
real_pathdup() function, which may return NULL. Since we
don't check the return value, we can segfault.
This is hard to trigger in practice, since we check that the
path is accessible before creating the alternate_object_database
struct. But it could be removed racily, or we could see a
transient filesystem error.
We could restore the original behavior by switching back to
xstrdup(real_path()). However, dying is probably not the
best option here. This whole function is best-effort
already; there might not even be a repository around the
shared objects at all. And if the alternate store has gone
away, there are no objects to show.
So let's just quietly return, as we would if we failed to
open "refs/", or if upload-pack failed to start, etc.
Signed-off-by: Jeff King <redacted>
---
transport.c | 2 ++
1 file changed, 2 insertions(+)
From: Jeff King <hidden> Date: 2017-02-08 20:59:37
The real_pathdup() function will have removed extra slashes
for us already (on top of the normalize_path() done when we
created the alternate_object_database struct in the first
place).
Incidentally, this also fixes the case where the path is
just "/", which would read off the start of the array.
That doesn't seem possible to trigger in practice, though,
as link_alt_odb_entry() blindly eats trailing slashes,
including a bare "/".
Signed-off-by: Jeff King <redacted>
---
transport.c | 2 --
1 file changed, 2 deletions(-)
@@ -1226,8 +1226,6 @@ static int refs_from_alternate_cb(struct alternate_object_database *e,return0;len=strlen(other);-while(other[len-1]=='/')-other[--len]='\0';if(len<8||memcmp(other+len-8,"/objects",8))gotoout;/* Is this a git repository with refs? */
From: Jeff King <hidden> Date: 2017-02-08 20:59:45
Breaking down the fields in the interface makes it easier to
change the backend of for_each_alternate_ref to something
that doesn't use "struct ref" internally.
The only field that callers actually look at is the oid,
anyway. The refname is kept in the interface as a plausible
thing for future code to want.
Signed-off-by: Jeff King <redacted>
---
builtin/receive-pack.c | 6 ++++--
fetch-pack.c | 12 ++++++++----
transport.c | 2 +-
transport.h | 2 +-
4 files changed, 14 insertions(+), 8 deletions(-)
From: Jeff King <hidden> Date: 2017-02-08 20:59:48
We have a string with ".../objects" pointing to the
alternate object store, and overwrite bits of it to look at
other paths in the (potential) git repository holding it.
This works because the only path we care about is "refs",
which is shorter than "objects".
Using a strbuf to hold the path lets us get rid of some
magic numbers, and makes it more obvious that the memory
operations are safe.
Signed-off-by: Jeff King <redacted>
---
transport.c | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
@@ -1214,34 +1214,34 @@ struct alternate_refs_data {staticintrefs_from_alternate_cb(structalternate_object_database*e,void*data){-char*other;-size_tlen;+structstrbufpath=STRBUF_INIT;+size_tbase_len;structremote*remote;structtransport*transport;conststructref*extra;structalternate_refs_data*cb=data;-other=real_pathdup(e->path);-if(!other)-return0;-len=strlen(other);--if(len<8||memcmp(other+len-8,"/objects",8))+if(!strbuf_realpath(&path,e->path,0))+gotoout;+if(!strbuf_strip_suffix(&path,"/objects"))gotoout;+base_len=path.len;+/* Is this a git repository with refs? */-memcpy(other+len-8,"/refs",6);-if(!is_directory(other))+strbuf_addstr(&path,"/refs");+if(!is_directory(path.buf))gotoout;-other[len-8]='\0';-remote=remote_get(other);-transport=transport_get(remote,other);+strbuf_setlen(&path,base_len);++remote=remote_get(path.buf);+transport=transport_get(remote,path.buf);for(extra=transport_get_remote_refs(transport);extra;extra=extra->next)cb->fn(extra,cb->data);transport_disconnect(transport);out:-free(other);+strbuf_release(&path);return0;}
From: Jeff King <hidden> Date: 2017-02-08 20:59:52
The current method for getting the refs from an alternate is
to run upload-pack in the alternate and parse its output
using the normal transport code. This works and is
reasonably short, but it has a very bad memory footprint
when there are a lot of refs in the alternate. There are two
problems:
1. It reads in all of the refs before passing any back to
us. Which means that our peak memory usage has to store
every ref (including duplicates for peeled variants),
even if our callback could determine that some are not
interesting (e.g., because they point to the same sha1
as another ref).
2. It allocates a "struct ref" for each one. Among other
things, this contains 3 separate 20-byte oids, along
with the name and various pointers. That can add up,
especially if the callback is only interested in the
sha1 (which it can store in a sha1_array as just 20
bytes).
On a particularly pathological case, where the alternate had
over 80 million refs pointing to only around 60,000 unique
objects, the peak heap usage of "git clone --reference" grew
to over 25GB.
This patch instead calls git-for-each-ref in the alternate
repository, and passes each line to the callback as we read
it. That drops the peak heap of the same command to 50MB.
I considered and rejected a few alternatives.
We could read all of the refs in the alternate using our own
ref code, just as we do with submodules. However, as memory
footprint is one of the concerns here, we want to avoid
loading those refs into our own memory as a whole.
It's possible that this will be a better technique in the
future when the ref code can more easily iterate without
loading all of packed-refs into memory.
Another option is to keep calling upload-pack, and just
parse its output ourselves in a streaming fashion. Besides
for-each-ref being simpler (we get to define the format
ourselves, and don't have to deal with speaking the git
protocol), it's more flexible for possible future changes.
For instance, it might be useful for the caller to be able
to limit the set of "interesting" alternate refs. The
motivating example is one where many "forks" of a particular
repository share object storage, and the shared storage has
refs for each fork (which is why so many of the refs are
duplicates; each fork has the same tags). A plausible
future optimization would be to ask for the alternate refs
for just _one_ fork (if you had some out-of-band way of
knowing which was the most interesting or important for the
current operation).
Similarly, no callbacks actually care about the symref value
of alternate refs, and as before, this patch ignores them
entirely. However, if we wanted to add them, for-each-ref's
"%(symref)" is going to be more flexible than upload-pack,
because the latter only handles the HEAD symref due to
historical constraints.
There is one potential downside, though: unlike upload-pack,
our for-each-ref command doesn't report the peeled value of
refs. The existing code calls the alternate_ref_fn callback
twice for tags: once for the tag, and once for the peeled
value with the refname set to "ref^{}".
For the callers in fetch-pack, this doesn't matter at all.
We immediately peel each tag down to a commit either way (so
there's a slight improvement, as do not bother passing the
redundant data over the pipe). For the caller in
receive-pack, it means we will not advertise the peeled
values of tags in our alternate. However, we also don't
advertise peeled values for our _own_ tags, so this is
actually making things more consistent.
It's unclear whether receive-pack advertising peeled values
is a win or not. On one hand, giving more information to the
other side may let it omit some objects from the push. On
the other hand, for tags which both sides have, they simply
bloat the advertisement. The upload-pack advertisement of
git.git is about 30% larger than the receive-pack
advertisement due to its peeled information.
This patch omits the peeled information from
for_each_alternate_ref entirely, and leaves it up to the
caller whether they want to dig up the information.
Signed-off-by: Jeff King <redacted>
---
transport.c | 48 ++++++++++++++++++++++++++++++++++++++----------
1 file changed, 38 insertions(+), 10 deletions(-)
From: Jeff King <hidden> Date: 2017-02-08 21:01:28
If you have an alternate object store with a very large
number of refs, the peak memory usage of the sha1_array can
grow high, even if most of them are duplicates that end up
not being printed at all.
The similar for_each_alternate_ref() code-paths in
fetch-pack solve this by using flags in "struct object" to
de-duplicate (and so are relying on obj_hash at the core).
But we don't have a "struct object" at all in this case. We
could call lookup_unknown_object() to get one, but if our
goal is reducing memory footprint, it's not great:
- an unknown object is as large as the largest object type
(a commit), which is bigger than an oidset entry
- we can free the memory after our ref advertisement, but
"struct object" entries persist forever (and the
receive-pack may hang around for a long time, as the
bottleneck is often client upload bandwidth).
So let's use an oidset. Note that unlike a sha1-array it
doesn't sort the output as a side effect. However, our
output is at least stable, because for_each_alternate_ref()
will give us the sha1s in ref-sorted order.
In one particularly pathological case with an alternate that
has 60,000 unique refs out of 80 million total, this reduced
the peak heap usage of "git receive-pack . </dev/null" from
13GB to 14MB.
Signed-off-by: Jeff King <redacted>
---
builtin/receive-pack.c | 26 ++++++++++++--------------
1 file changed, 12 insertions(+), 14 deletions(-)
From: Jeff King <hidden> Date: 2017-02-08 21:01:31
This is similar to many of our uses of sha1-array, but it
overcomes one limitation of a sha1-array: when you are
de-duplicating a large input with relatively few unique
entries, sha1-array uses 20 bytes per non-unique entry.
Whereas this set will use memory linear in the number of
unique entries (albeit a few more than 20 bytes due to
hashmap overhead).
Signed-off-by: Jeff King <redacted>
---
Makefile | 1 +
oidset.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
oidset.h | 45 +++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 95 insertions(+)
create mode 100644 oidset.c
create mode 100644 oidset.h
From: Jeff King <hidden> Date: 2017-02-08 21:01:34
We may run for_each_alternate_ref() twice, once in
find_common() and once in everything_local(). This operation
can be expensive, because it involves running a sub-process
which must freshly load all of the alternate's refs from
disk.
Let's cache and reuse the results between the two calls. We
can make some optimizations based on the particular use
pattern in fetch-pack to keep our memory usage down.
The first is that we only care about the sha1s, not the refs
themselves. So it's OK to store only the sha1s, and to
suppress duplicates. The natural fit would therefore be a
sha1_array.
However, sha1_array's de-duplication happens only after it
has read and sorted all entries. It still stores each
duplicate. For an alternate with a large number of refs
pointing to the same commits, this is a needless expense.
Instead, we'd prefer to eliminate duplicates before putting
them in the cache, which implies using a hash. We can
further note that fetch-pack will call parse_object() on
each alternate sha1. We can therefore keep our cache as a
set of pointers to "struct object". That gives us a place to
put our "already seen" bit with an optimized hash lookup.
And as a bonus, the object stores the sha1 for us, so
pointer-to-object is all we need.
There are two extra optimizations I didn't do here:
- we actually store an array of pointer-to-object.
Technically we could just walk the obj_hash table
looking for entries with the ALTERNATE flag set (because
our use case doesn't care about the order here).
But that hash table may be mostly composed of
non-ALTERNATE entries, so we'd waste time walking over
them. So it would be a slight win in memory use, but a
loss in CPU.
- the items we pull out of the cache are actual "struct
object"s, but then we feed "obj->sha1" to our
sub-functions, which promptly call parse_object().
This second parse is cheap, because it starts with
lookup_object() and will bail immediately when it sees
we've already parsed the object. We could save the extra
hash lookup, but it would involve refactoring the
functions we call. It may or may not be worth the
trouble.
Signed-off-by: Jeff King <redacted>
---
fetch-pack.c | 52 ++++++++++++++++++++++++++++++++++++++++++----------
object.h | 2 +-
2 files changed, 43 insertions(+), 11 deletions(-)
From: Jeff King <hidden> Date: 2017-02-08 21:01:37
The comment claims that we handle alternate ".have" lines
through this function, but that hasn't been the case since
85f251045 (write_head_info(): handle "extra refs" locally,
2012-01-06).
Signed-off-by: Jeff King <redacted>
---
builtin/receive-pack.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
From: Jeff King <hidden> Date: 2017-02-08 21:01:38
Namely, de-duplicate them. We use the same set as the
alternates, since we call them both ".have" (i.e., there is
no value in showing one versus the other).
Signed-off-by: Jeff King <redacted>
---
builtin/receive-pack.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
From: Jeff King <hidden> Date: 2017-02-08 21:01:41
We de-duplicate ".have" refs among themselves, but never
check if they are duplicates of our local refs. It's not
unreasonable that they would be if we are a "--shared" or
"--reference" clone of a similar repository; we'd have all
the same tags.
We can handle this by inserting our local refs into the
oidset, but obviously not suppressing duplicates (since the
refnames are important).
Note that this also switches the order in which we advertise
refs, processing ours first and then any alternates. The
order shouldn't matter (and arguably showing our refs first
makes more sense).
Signed-off-by: Jeff King <redacted>
---
builtin/receive-pack.c | 4 +++-
t/t5400-send-pack.sh | 38 ++++++++++++++++++++++++++++++++++++++
2 files changed, 41 insertions(+), 1 deletion(-)
@@ -255,4 +255,42 @@ test_expect_success 'deny pushing to delete current branch' ')'+extract_ref_advertisement(){+perl-lne'+# \\ is there to skip capabilities after \0+/push<([^\\]+)/ornext;+exit0if$1eq"0000";+print$1;+'+}++test_expect_success'receive-pack de-dupes .have lines''+gitinitshared&&+git-Csharedcommit--allow-empty-mboth&&+gitclone-ssharedfork&&+(+cdshared&&+gitcheckout-bonly-shared&&+gitcommit--allow-empty-monly-shared&&+gitupdate-refrefs/heads/fooHEAD+)&&++# Notable things in this expectation:+# - local refs are not de-duped+# - .have does not duplicate locals+# - .have does not duplicate itself+local=$(git-Cforkrev-parseHEAD)&&+shared=$(git-Csharedrev-parseonly-shared)&&+cat>expect<<-EOF&&+$localrefs/heads/master+$localrefs/remotes/origin/HEAD+$localrefs/remotes/origin/master+$shared.have+EOF++GIT_TRACE_PACKET=$(pwd)/tracegitpushforkHEAD:foo&&+extract_ref_advertisement<trace>refs&&+test_cmpexpectrefs+'+ test_done