git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Stephen Morton <stephen.c.morton@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Slow git pushes: sitting 1 minute in pack-objects
Date: Mon, 9 Mar 2015 03:53:02 -0400	[thread overview]
Message-ID: <20150309075302.GB31866@peff.net> (raw)
In-Reply-To: <CAH8BJxH1uVv9J7yLx1D4GRPKfWYqDw8SRFZKGR_yhjcoTCCT2g@mail.gmail.com>

On Thu, Mar 05, 2015 at 04:03:07PM -0500, Stephen Morton wrote:

> I'm experiencing very slow git pushes. On the order of 1 minute to push a
> trivial one-line change. When I set GIT_TRACE=1, I see that it seems to be
> taking a lot of time in the pack-objects phase.

Can you tell what pack-objects is doing? Perhaps "strace -f -tt" might
help. Or even just "time git push", which will tell us whether we're
spinning on CPU or something else.

If you watch the progress meter, where does it spend its time? In
"counting objects", "compressing objects", or "writing objects"? Or
after that?

You said the repo is big. Is it reasonably packed (try running `git
gc`). Pack-objects may look at objects that you know the other side has
in order to create deltas against them. If you have some crazy situation
(e.g., you have several thousand packfiles) that can slow down object
access quite a bit. A minute is more than I would expect, but if VFS
operations in your VM are slow, that could be it.

-Peff

  parent reply	other threads:[~2015-03-09  7:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 21:03 Slow git pushes: sitting 1 minute in pack-objects Stephen Morton
2015-03-06  0:25 ` Duy Nguyen
2015-03-06  0:37   ` Stephen Morton
2015-03-09  7:53 ` Jeff King [this message]
2015-03-10  1:37   ` Stephen Morton
2015-03-16 22:15     ` Jeff King
2015-03-19 20:31       ` Stephen Morton
2015-03-19 21:07         ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150309075302.GB31866@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=stephen.c.morton@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).