Re: Seems to be pushing more than necessary
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Mar 18, 2015, 11:42 UTC
- Message-ID
- <CACsJy8DdjDnacVGU83iUDj5Na1xxS6kNDbK2D0Apfv0LAuzDvA@mail.gmail.com>
- In-Reply-To
- <CAABECY2_MQWAkOu=6rR=mN=wKz-Yfzsu8o2+wb6F+h4FjBe9Mw@mail.gmail.com>
On Wed, Mar 18, 2015 at 6:26 PM, Graham Hay <grahamrhay@gmail.com> wrote:
Show 8 quoted lines
>> It would help if you pasted the push output. For example, does it stop >> at 20% at the "compressing objects" line or "writing objects". How >> many total objects does it say? > > It rattles through "compressing objects", and the first 20% of > "writing objects", then slows to a crawl. > > Writing objects: 33% (3647/10804), 80.00 MiB | 112.00 KiB/s
This 10804 looks wrong (i.e. sending that many compressed objects). Also "80 MiB" sent at that point. If you modify just a couple files, something is really wrong because the number of new objects may be hundreds at most, not thousands.
v2.2.2 supports "git fast-export --anonymize" [1] to create an anonymized "clone" of your repo that you can share, which might help us understand the problem.
There's also the environment variable GIT_TRACE_PACKET that can help see what's going on at the protocol level, but I think you're on your own because without access to this repo, SHA-1s from that trace may not make much sense.
[1] https://github.com/git/git/commit/a8722750985a53cc502a66ae3d68a9e42c7fdb98
-- Duy