> Pegging CPU for a few seconds doesn't sound out-of-place for
> pack-objects serving a fetch or clone on a large repository. And I can
> certainly believe "minutes", especially if it was not serving a fetch,
> but doing repository maintenance on a large repository.
>
> Talk to GitHub Enterprise su
> * Consider having that queue of yours just send the pushed payload
> instead of "pull this", see git-bundle. This can turn this sync entire
> thing into a static file distribution problem.
As far as I know, GHE doesn't support this out of the box. We've asked
them for essentially this, though.
> So your load is probably really spiky, as you get thundering herds of
> fetchers after every push (the spikes may have a long flatline at the
> top, as it takes time to process the whole herd).
It is quite spiky, yes. At the moment, however, the replication fleet
is relatively small (at the mome
My assumption is that pack bitmaps are enabled since the primary
server is a GitHub Enterprise instance, but I'll have to confirm.
On Sun, Aug 28, 2016 at 2:20 PM, Jakub Narębski wrote:
> W dniu 28.08.2016 o 21:42, W. David Jarvis pisze:
>
>> The ultimate goal for us is just fi
Hi all -
I've run into a problem that I'm looking for some help with. Let me
describe the situation, and then some thoughts.
The company I work for uses git. We use GitHub Enterprise as a
frontend for our primary git server. We're using Chef solo to manage a
fleet of upwards of 10,000 hosts, whic
5 matches
Mail list logo
