On Wed, Apr 27, 2016 at 09:53:24PM +0000, Eric Wong wrote:
> It can be tempting for a server admin to want a stable set of
> long-lived packs for dumb clients; but also want to enable
> bitmaps to serve smart clients more quickly.
>
> Unfortunately, such a configuration is impossible;
> so at least warn users of this incompatibility since
> commit 21134714787a02a37da15424d72c0119b2b8ed71
> ("pack-objects: turn off bitmaps when we split packs").
>
> Tested the warning by inspecting the output of:
>
> make -C t t5310-pack-bitmaps.sh GIT_TEST_OPTS=-v
I think the intent and code in your patch is fine; looks like doc
specifics are being discussed elsewhere.
But I did want to mention one thing, which is that long-lived split
packs are a tradeoff, even for dumb clients. The pack format cannot do
deltas between packs, so the sum of your split packs is larger than a
single pack would be. That's a good thing for somebody who cloned
earlier, and wants to only a few small packs on top. But it's much worse
for somebody who wants to do a fresh clone, and has to grab all of the
packs either way.
> Fwiw, I'm hoping to publish an ~800MB git-clone-able repo of
> our ML archives, soonish. I can serve terabytes of dumb HTTP
> traffic all day long without breaking a sweat; but smart
> packing of big repos worries me; especially when feeding
> slow clients and having to leave processes running
> (or buffering pack output to disk). So perhaps I'll teach
> my HTTP server play dumb whenever CPU/memory usage is high.
Yeah, CPU and memory load for serving large clones is a problem. Memory
especially scales with number of objects (because we keep the whole
packing list in memory for the entirety of the write). At GitHub, we
have some changes to try to serve things verbatim from the on-disk pack
without even creating an in-memory list of objects (it's just a bitmap
of which objects in the packfile to send), and that reduces CPU and
memory load quite a bit. Cleaning up and submitting those patches has
been on my todo list for a while, but I just haven't gotten to it. I'm
of course happy to share the messy state if you want to pick through it
yourself.
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html