From: Michael Yartys <michael.yartys@protonmail.com>
To: Simon Barber <simon@superduper.net>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"make-wifi-fast@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Bufferbloat on Norwegian train wifi
Date: Mon, 22 Jun 2020 21:14:32 +0000 [thread overview]
Message-ID: <ICJYwMjbIk-Cj7EAJ6y8m4aJHgtDa2cvAI8pS8JoT4PC_dAAxG70JC2J3uZDubPRIg4m5sr4GwaCdhcSX3gHMxi0vXs2feBoK7MvLPBaWn0=@protonmail.com> (raw)
In-Reply-To: <A81112B8-1CA0-41BE-8664-3FD590F8F479@superduper.net>
Wow, those are some truly crappy networks!
I'll try to contact Vy to get them to do something about it. I wonder how much of this might be due to the equipment on their trains though. I decided to measure the bufferbloat on the LTE network in my neighbourhood, and on average I got 300 ms above baseline while running an 8-stream TCP download. Then again, I ran this test with my phone acting as a hotspot, and the results might be affected by that. Does anybody know if this methodology produces reliable results? I presume that even the very short peak of 86 Mbps shouldn't really cause much WiFi-related bufferbloat.
Michael
next prev parent reply other threads:[~2020-06-22 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.607.1592728703.24343.make-wifi-fast@lists.bufferbloat.net>
2020-06-22 12:51 ` Toke Høiland-Jørgensen
2020-06-22 20:29 ` Simon Barber
2020-06-22 21:14 ` Michael Yartys [this message]
2020-06-23 10:11 ` Toke Høiland-Jørgensen
2020-06-24 8:56 ` Michael Yartys
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://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ICJYwMjbIk-Cj7EAJ6y8m4aJHgtDa2cvAI8pS8JoT4PC_dAAxG70JC2J3uZDubPRIg4m5sr4GwaCdhcSX3gHMxi0vXs2feBoK7MvLPBaWn0=@protonmail.com' \
--to=michael.yartys@protonmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=simon@superduper.net \
--cc=toke@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