From: Jeff King <peff@peff.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git <git@vger.kernel.org>
Subject: Re: No progress from push when using bitmaps
Date: Thu, 13 Mar 2014 17:26:26 -0400 [thread overview]
Message-ID: <20140313212626.GA23618@sigill.intra.peff.net> (raw)
In-Reply-To: <CAJo=hJth1YB+u2Y9S0X3xk7s2-HcPP4_k03qprHBU4A9721i8g@mail.gmail.com>
On Wed, Mar 12, 2014 at 05:21:21PM -0700, Shawn Pearce wrote:
> Today I tried pushing a copy of linux.git from a client that had
> bitmaps into a JGit server. The client stalled for a long time with no
> progress, because it reused the existing pack. No progress appeared
> while it was sending the existing file on the wire:
>
> $ git push git://localhost/linux.git master
> Reusing existing pack: 2938117, done.
> Total 2938117 (delta 0), reused 0 (delta 0)
> remote: Resolving deltas: 66% (1637269/2455727)
>
> This is not the best user experience. :-(
Yeah, I agree that sucks. I hadn't noticed it, as I don't typically have
my client repos bitmapped (and on fetch, the interesting progress is
coming from the local index-pack).
It would definitely be good to have throughput measurements while
writing out the pack. However, I'm not sure we have anything useful to
count. We know the total number of objects we're reusing, but we're not
actually parsing the data; we're just blitting it out as a stream. I
think the progress code will need some refactoring to handle a
throughput-only case.
-Peff
next prev parent reply other threads:[~2014-03-13 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 0:21 No progress from push when using bitmaps Shawn Pearce
2014-03-13 21:26 ` Jeff King [this message]
2014-03-13 22:01 ` Shawn Pearce
2014-03-13 22:07 ` Jeff King
2014-03-13 22:23 ` Junio C Hamano
2014-03-13 22:24 ` Jeff King
2014-03-14 9:43 ` Michael Haggerty
2014-03-14 10:21 ` Duy Nguyen
2014-03-14 15:29 ` Jeff King
2014-03-14 23:53 ` Duy Nguyen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140313212626.GA23618@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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.
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 NNTP newsgroup(s).