From: Daniel Koverman <dkoverman@predictiveTechnologies.com>
To: Jeff King <peff@peff.net>
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: Tue, 8 Dec 2015 17:34:43 +0000 [thread overview]
Message-ID: <8712f730fb4c414ebc2b1168ca7948b8@EXCHANGE1U.uunet.arlington.PredictiveTechnologies.com> (raw)
In-Reply-To: <20151207225714.GA3785@sigill.intra.peff.net>
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
capitalizing on my knowledge of this particular repository to come
up with heuristics for picking a reasonable subset. This will
come with the risk of sometimes producing an unnecessarily large
(potentially an obscenely large) packfile. You have thoroughly
convinced me that an option like that will not generalize and would
be unsuitable for main line git.
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.
Thanks again, Junio and Peff.
Daniel
-----Original Message-----
From: Jeff King [mailto:peff@peff.net]
Sent: Monday, December 07, 2015 5:57 PM
To: Daniel Koverman
Cc: Junio C Hamano; git@vger.kernel.org
Subject: Re: Why does send-pack call pack-objects for all remote refs?
On Mon, Dec 07, 2015 at 02:41:00PM -0800, Junio C Hamano wrote:
> Also it was unclear if you are working with a shallow repository.
> The performance trade-off made between the packsize and the cycles
> is somewhat different between a normal and a shallow repository,
> e.g. 2dacf26d (pack-objects: use --objects-edge-aggressive for
> shallow repos, 2014-12-24) might be a good starting point to think
> about this issue.
Also note that for a while the "aggressive" form was used everywhere. I
think that started in fbd4a70 (list-objects: mark more commits as edges
in mark_edges_uninteresting - 2013-08-16), and was fixed in 1684c1b
(rev-list: add an option to mark fewer edges as uninteresting,
2014-12-24).
So it was present from v1.8.4.2 up to v2.3.0.
-Peff
next prev parent reply other threads:[~2015-12-08 18:01 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 [this message]
2015-12-10 4:19 ` Jeff King
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=8712f730fb4c414ebc2b1168ca7948b8@EXCHANGE1U.uunet.arlington.PredictiveTechnologies.com \
--to=dkoverman@predictivetechnologies.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).