On Thu, Dec 11, 2014 at 08:41:07AM +0700, Duy Nguyen wrote:
> It could be a regression by fbd4a70 (list-objects: mark more commits
> as edges in mark_edges_uninteresting - 2013-08-16). That commit makes
> --thin a lot more agressive (reading lots of trees). You can try to
> revert that commit (or u
On Thu, Dec 11, 2014 at 6:34 AM, brian m. carlson
wrote:
> I looked at this more in depth today and I found that the bottleneck is
> --thin. I tried git send-pack, which does not use --thin by default,
> which led me to further testing. A particular push went from 24 seconds
> with --thin to 4 s
On Tue, Dec 09, 2014 at 09:41:28PM -0800, Shawn Pearce wrote:
> On Tue, Dec 9, 2014 at 4:37 PM, brian m. carlson
> wrote:
> > Most of the time is spent between the "Pushing to remote machine" and
> > "Counting objects", running git pack-objects:
> >
> > git pack-objects --all-progress-implied --
On Wed, Dec 10, 2014 at 7:37 AM, brian m. carlson
wrote:
> I have a repository that's just under 2 GiB in size and contains over
> 2 refs, with a copy of it on a server. Both sides are using Git
> 2.1.2. If I push a branch that contains a single commit, it takes about
> 15 seconds to push.
On Tue, Dec 9, 2014 at 4:37 PM, brian m. carlson
wrote:
> I have a repository that's just under 2 GiB in size and contains over
> 2 refs, with a copy of it on a server. Both sides are using Git
> 2.1.2. If I push a branch that contains a single commit, it takes about
> 15 seconds to push. H
I have a repository that's just under 2 GiB in size and contains over
2 refs, with a copy of it on a server. Both sides are using Git
2.1.2. If I push a branch that contains a single commit, it takes about
15 seconds to push. However, if everything is up-to-date, it completes
within 2 second
6 matches
Mail list logo
