From: Junio C Hamano <junkio@cox.net>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] send-pack: allow skipping delta when sending pack
Date: Sun, 21 May 2006 02:40:46 -0700 [thread overview]
Message-ID: <7vpsi7yau9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20060521084313.GA12825@coredump.intra.peff.net
Jeff King <peff@peff.net> writes:
> What do you suggest for this performance issue, then?
> A manual no-delta trigger, or just going to get a cup of coffee while
> pushing (my tests showed 5-6x slowdown from deltifying)?
In the short term, give --depth to send-pack, would be better
than nothing.
I agree we should be able to do better. But let me grab some
sleep now first ;-).
prev parent reply other threads:[~2006-05-21 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 5:48 [RFC] send-pack: allow skipping delta when sending pack Jeff King
2006-05-21 6:17 ` Junio C Hamano
2006-05-21 8:14 ` Jeff King
2006-05-21 8:24 ` Jakub Narebski
2006-05-21 8:44 ` Jeff King
2006-05-21 9:14 ` Junio C Hamano
2006-05-21 9:24 ` Jakub Narebski
2006-05-21 8:31 ` Junio C Hamano
2006-05-21 8:43 ` Jeff King
2006-05-21 9:40 ` Junio C Hamano [this message]
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=7vpsi7yau9.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).