From: Wilko Meyer <w@wmeyer.eu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Nicolas Graves <ngraves@ngraves.fr>, guix-devel@gnu.org
Subject: Re: Guix / Nix Benchmarks
Date: Mon, 03 Jul 2023 00:02:40 +0200 [thread overview]
Message-ID: <874jmmarb9.fsf@wmeyer.eu> (raw)
In-Reply-To: <87zg4et2dm.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> I’ve found download speeds to vary wildly dependent on where you are.
> From an AWS EC2 instance in Frankfurt we get about 50MiB/s download
> speeds from ci.guix.gnu.org, whereas some in France get sub 1MiB/s.
So, this could be an ISP related issue, e.g. maybe an issue regarding
peering capacities? As far as I know there have been historical issues
in this direction between commerical ISPs (namely DTAG being the one I'm
aware of) and educational networks such as X-WiN, so (without having any
deeper knowledge on Guixes situation on this) this could apply here as
well?
As ci.guix.gnu.org is hosted at AS210482/the Max-Delbrueck-Centrum, I
would guess that there could be something similar going on causing this,
e.g. commerical ISP trying to enforce their double payed traffic
strategies and the educational networks where ci.guix.gnu.org is hosted
(rightfully) not participating in that/not having direct peering with
these ISPs ASNs?
Regards,
Wilko Meyer
next prev parent reply other threads:[~2023-07-09 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 12:54 Guix / Nix Benchmarks Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-06-19 18:55 ` kiasoc5
2023-06-20 5:24 ` Csepp
2023-06-20 9:14 ` Efraim Flashner
2023-06-20 10:45 ` W. T. Meyer
2023-06-20 14:48 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-07-02 20:30 ` Ludovic Courtès
2023-07-02 21:42 ` Ricardo Wurmus
2023-07-02 22:02 ` Wilko Meyer [this message]
2023-07-03 6:17 ` Ricardo Wurmus
2023-08-19 12:11 ` Simon Tournier
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jmmarb9.fsf@wmeyer.eu \
--to=w@wmeyer.eu \
--cc=guix-devel@gnu.org \
--cc=ngraves@ngraves.fr \
--cc=rekado@elephly.net \
/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://git.savannah.gnu.org/cgit/guix.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).