From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Stefan Beller <sbeller@google.com>
Cc: Eric Wong <e@80x24.org>, git <git@vger.kernel.org>,
meta@public-inbox.org
Subject: Re: "IMAP IDLE"-like long-polling "git fetch"
Date: Wed, 9 Jan 2019 17:49:09 -0500 [thread overview]
Message-ID: <20190109224909.GC8258@pure.paranoia.local> (raw)
In-Reply-To: <CAGZ79kb9Tbnxe1mSnxpqT_FO6Gdi6wxd-r2YarHXRF1sVRyxLA@mail.gmail.com>
On Wed, Jan 09, 2019 at 02:27:25PM -0800, Stefan Beller wrote:
> > > I would've thought somebody had done this by now, but I guess
> > > it's dependent on a bunch of things (TLS layer nowadays, maybe
> > > HTTP/2), so git-daemon support alone wouldn't cut it...
> >
> > Polling is not all bad, especially for large repository collections.
>
> I disagree with that statement.
>
> IIRC, More than half the bandwidth of Googles git servers are used
> for ls-remote calls (i.e. polling a lot of repos, most of them did *not*
> change, by build bots which are really eager to try again after a minute).
Oh, that's not the kind of polling I meant -- we monitor a single
manifest file containing the state of all repositories. It's a static
file served directly by any httpd daemon, and the only traffic is
usually the "not modified" http header.
-K
next prev parent reply other threads:[~2019-01-09 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181229034342.11543-1-e@80x24.org>
2018-12-29 3:56 ` "IMAP IDLE"-like long-polling "git fetch" Eric Wong
2018-12-29 4:38 ` Konstantin Ryabitsev
2018-12-29 6:13 ` Eric Wong
2019-01-09 22:27 ` Stefan Beller
2019-01-09 22:49 ` Konstantin Ryabitsev [this message]
2019-05-02 8:50 ` Eric Wong
2019-05-02 9:21 ` Ævar Arnfjörð Bjarmason
2019-05-02 9:42 ` Eric Wong
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=20190109224909.GC8258@pure.paranoia.local \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=meta@public-inbox.org \
--cc=sbeller@google.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.