> 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
>
> Another question is how big are these binary files on average? Git
> considers a file is "big" if its size is 512MB or more (see
> core.bigFileThreshold). If your binary files are are mostly under this
> limit, but still big enough, then git may still try to compare new
> objects with these to find the smallest "diff" to send. If it's the
> case, you could set core.bigFileThreshold to cover these binary files.
None of the files are very big (KB rather than MB), but there's a lot
of them. I'll try setting the threshold to something lower, thanks.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
