qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	qemu-devel@nongnu.org
Subject: Re: qemu.org server bandwidth report (May 2021)
Date: Mon, 10 May 2021 16:47:41 +0100	[thread overview]
Message-ID: <8735uuy48m.fsf@linaro.org> (raw)
In-Reply-To: <CAJSP0QXMwSZqMRLXx3XYrrCe+OMP0k-hqFWb_GR_uMW35zZqDA@mail.gmail.com>


Stefan Hajnoczi <stefanha@gmail.com> writes:

> On Mon, May 10, 2021 at 11:31 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
>>
>> On Mon, May 10, 2021 at 10:49:19AM +0100, Stefan Hajnoczi wrote:
>>
>> > qemu.org bandwidth usage has been as follows:
>> > - Jan: 12.56 TB
>> > - Feb: 10.55 TB
>> > - Mar: 10.28 TB
>> > - Apr: 7.62 TB
>> >
>> > In May qemu.org has averaged 232.25 GB/day so far putting it on track
>> > for 7 TB total this month.
<snip>
>>
>> For the https:// URIs should we setup a HTTP redirect ?
>>
>> When git clones via https it fetches some specific paths which
>> I believe we have rules for in httpd conf:
>>
>>   ScriptAliasMatch "^/git/(.*\.git/(HEAD|info/refs))$" \
>>     /usr/libexec/git-core/git-http-backend/$1
>>   ScriptAliasMatch "^/git/(.*\.git/git-(upload|receive)-pack)$" \
>>     /usr/libexec/git-core/git-http-backend/$1
>>
>> If we set those URI path matches to send a HTTP 307 redirect
>> to gitlab, that would essentially kill off our git traffic on
>> qemu.org, while still allowing the qemu.org gitweb UI to
>> work normally. The downside is that people won't notice to
>> update their clone URIs. Still feels like an easy win and
>> we can easily remove the redirect if we use code 307.
>
> I remember there were concerns about warning messages that
> git-clone(1) prints when an HTTP redirect is encountered? If everyone
> is okay I can turn the git-http-backend(1) aliases into HTTP 307
> redirects to GitLab.
>
>> Third, qemu 4.2.0....
>>
>> I wonder why this is the most popular. Something must be linking
>> to this, as you would otherwise have to go out of your way to
>> search it out.
>>
>> Do we have any stats on the referrer URLs ?
>>
>> I wonder if there's some key page(s) that need updating ?
>>
>> If we're unlucky there might be some CI system that hardcoded
>> use of qemu 4.2.0 that's frequently pulling it.
>
> The majority of qemu-4.2.0.tar.xz downloads have the wget user agent
> and no referrer. The IP addresses don't have a clear pattern (there
> are many).

I've just checked my Gentoo box and I can see it pulls directly from:

  SRC_URI="https://download.qemu.org/${P}.tar.xz"

and the *9999* builds (HEAD, which I doubt many people use) points to:

  EGIT_REPO_URI="https://git.qemu.org/git/qemu.git"

but the lowest version is 5.2.0 and 6.0.0 is already in the repo so
these particular users probably are a minority.

However Google does point to a number of instructions online that have
wget and "qemu-4.2.0.tar.xz" in them. 

>
> Stefan


-- 
Alex Bennée


  parent reply	other threads:[~2021-05-10 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10  9:49 qemu.org server bandwidth report (May 2021) Stefan Hajnoczi
2021-05-10 10:31 ` Daniel P. Berrangé
2021-05-10 13:40   ` Stefan Hajnoczi
2021-05-10 13:46     ` Daniel P. Berrangé
2021-05-10 15:47     ` Alex Bennée [this message]
2021-05-10 16:05       ` Stefan Hajnoczi

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=8735uuy48m.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=thuth@redhat.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 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 NNTP newsgroup(s).