From: Jeff King <peff@peff.net>
To: Daniel Koverman <dkoverman@predictiveTechnologies.com>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Why does send-pack call pack-objects for all remote refs?
Date: Wed, 9 Dec 2015 23:19:42 -0500 [thread overview]
Message-ID: <20151210041941.GA4056@sigill.intra.peff.net> (raw)
In-Reply-To: <8712f730fb4c414ebc2b1168ca7948b8@EXCHANGE1U.uunet.arlington.PredictiveTechnologies.com>
On Tue, Dec 08, 2015 at 05:34:43PM +0000, Daniel Koverman wrote:
> Your interpretation of my email was correct. As you picked up on, I
> had a fundamental misunderstanding of what pack-objects was doing.
> Thanks for the explanation, I have a much better idea of what is
> going on now.
>
> Given my use pattern, it may be reasonable for me to patch in an
> option to compute
>
> git rev-list --objects $my_topic --not $subset_of_remote_refs
You might also try repacking with "git repack -adb", which will build
reachability bitmaps. Pack-objects can use them to compute the set of
required objects much faster.
> It is also good to know that 2000 remote refs is insane. The lower
> hanging fruit here sounds like trimming that to a reasonable
> number, so I'll try that approach first.
It's definitely a lot, but it's not unheard of. The git project has over
500 tags. That's not 2000, but you're within an order of magnitude.
I have seen repositories with 20,000+ tags. I consider that a bit more
ridiculous, but it does work in practice.
-Peff
next prev parent reply other threads:[~2015-12-10 4:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 21:02 Why does send-pack call pack-objects for all remote refs? Daniel Koverman
2015-12-07 22:41 ` Junio C Hamano
2015-12-07 22:57 ` Jeff King
2015-12-08 17:34 ` Daniel Koverman
2015-12-10 4:19 ` Jeff King [this message]
2015-12-12 4:15 ` Nasser Grainawi
2015-12-14 13:47 ` Daniel Koverman
2015-12-14 21:04 ` Jeff King
2015-12-14 22:31 ` Jonathan Nieder
2015-12-14 22:37 ` 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=20151210041941.GA4056@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dkoverman@predictiveTechnologies.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).