From: Taylor Blau <me@ttaylorr.com>
To: Christian Schilling <christian.schilling.de@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: ls-refs protocol extension
Date: Sun, 24 Jan 2021 20:04:56 -0500 [thread overview]
Message-ID: <YA4ZOOccXK0YEOWu@nand.local> (raw)
In-Reply-To: <CAJsFKUCuvO7Y7-MJZ-GG9Jv+4-ei=-tvx4PF1PbeU61m+CV9RA@mail.gmail.com>
On Sun, Jan 24, 2021 at 01:40:08PM +0100, Christian Schilling wrote:
> Hi list,
> I have been working on a custom git server where the sha values
> required to respond to a ls-refs command can occasionally be expensive
> to compute.
Almost certainly the expensive part of ls-refs is actually traversing
the references, not parsing the objects they point at and determining
their hash.
Incidentally, we had a discussion recently [1] that resulted in some
patches that make it so that ls-refs often only has to read through part
of the refs in your repository, not all of them.
> It would be a great improvement of user experience if it was possible
> to show progress to the user while this is happening.
It's possible that that might help, but honestly I'd be surprised if
there was a real use-case that needed it (especially after the patches
that I mentioned which should make it fast enough that you don't have to
care :-)).
Thanks,
Taylor
[1]: https://lore.kernel.org/git/20210119144251.27924-1-jacob@gitlab.com/
next prev parent reply other threads:[~2021-01-25 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 12:40 ls-refs protocol extension Christian Schilling
2021-01-25 1:04 ` Taylor Blau [this message]
2021-01-25 8:44 ` Christian Schilling
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=YA4ZOOccXK0YEOWu@nand.local \
--to=me@ttaylorr.com \
--cc=christian.schilling.de@gmail.com \
--cc=git@vger.kernel.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.
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).