qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	danpb@redhat.com, "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: qemu.org server bandwidth report (May 2021)
Date: Mon, 10 May 2021 10:49:19 +0100	[thread overview]
Message-ID: <CAJSP0QXLcsRy8yONRyh8ZzmFJHALwRKqPa5m52TTL4h5iBZcmg@mail.gmail.com> (raw)

Hi,
A few months ago qemu.org hit network bandwidth limits and incurred
costs for exceeding them. Since then we have implemented several
changes to make continuous integration systems more
bandwidth-efficient and reduce the biggest sources of traffic to
qemu.org.

During the Mar-Apr billing cycle qemu.org still exceeded its network
bandwidth limit but only by a small amount. Bandwidth consumption
needs to be under ~6-7 TB/month. Below are the details of how we're
doing.

Thank you to Paolo Bonzini, Thomas Huth, Philippe Mathieu-Daudé,
Daniel Berrangé, and everyone who helped with bandwidth reduction. The
main change was a move to GitLab.com, which now serves the main QEMU
git repository URLs. We also updated documentation and links to
encourage people to use these new URLs.

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.

The top 3 web traffic users are Google Cloud and Amazon Web Services
IP addresses. This suggests that some continuous integration systems
are still accessing qemu.org git repositories. It is unlikely that
these are crawlers because User-Agent web stats show that crawlers
only consume a few GB whereas the top three hosts consume 10s or 100s
of GB each.

Roughly 75% of traffic is git (https), 25% is tarball downloads, and
the rest is wiki/web/miscellaneous traffic. Fun fact:
qemu-4.2.0.tar.xz is the most popular download!

I will send another update in 2 months so we can see where bandwidth
usage finally settled. At that point we can decide whether more steps
are necessary.

Thanks,
Stefan


             reply	other threads:[~2021-05-10  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10  9:49 Stefan Hajnoczi [this message]
2021-05-10 10:31 ` qemu.org server bandwidth report (May 2021) 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
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=CAJSP0QXLcsRy8yONRyh8ZzmFJHALwRKqPa5m52TTL4h5iBZcmg@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=danpb@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).