All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Tan <jonathantanmy@google.com>
To: johncai86@gmail.com
Cc: avarab@gmail.com, gitgitgadget@gmail.com, git@vger.kernel.org,
	jonathantanmy@google.com, gitster@pobox.com
Subject: Re: [PATCH] promisor-remote.c: use oidset for deduplication
Date: Tue, 25 Jan 2022 11:17:01 -0800	[thread overview]
Message-ID: <20220125191701.2649292-1-jonathantanmy@google.com> (raw)
In-Reply-To: <E5AD42A3-AEAC-44F8-B223-90E2ACAEFCB0@gmail.com>

John Cai <johncai86@gmail.com> writes:
> Jonathan, how often do we expect diff to pass duplicate oids to
> promisor_remote_get_direct()?

I don't recall all the details, but not often, I believe. In a partial
clone, I envision that you would typically diff one tree that you have
all blobs for and one tree that you don't (or two trees that you have
all blobs for). If a user is in a sparse checkout and/or they're diffing
two trees that they have never checked out, I would recommend disabling
inexact copy detection to reduce the number of blobs that Git would need
to fetch. In these cases, I think that diff would only pass duplicate
OIDs if one of the trees references the same object more than once
(directly or indirectly).

      reply	other threads:[~2022-01-25 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 20:32 [PATCH] promisor-remote.c: use oidset for deduplication John Cai via GitGitGadget
2022-01-13 23:45 ` Junio C Hamano
2022-01-14 12:11 ` Ævar Arnfjörð Bjarmason
2022-01-14 19:14   ` Junio C Hamano
2022-01-14 23:12     ` Junio C Hamano
2022-01-24 22:55   ` John Cai
2022-01-25 19:17     ` Jonathan Tan [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=20220125191701.2649292-1-jonathantanmy@google.com \
    --to=jonathantanmy@google.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=johncai86@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.