From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] teh tech guy has got bufferbloat bad on his link
Date: Wed, 12 Aug 2015 18:36:20 +0200 [thread overview]
Message-ID: <CAA93jw6VEZ7=RKiYREmgs=77PfGH0Ai2g1XqQ6=ie4mP32273g@mail.gmail.com> (raw)
but missed talking about it. Peaking at 600ms of delay at 100mbit,
shown at about 1:45.
see vlog at:
https://www.twit.tv/shows/the-tech-guy/episodes/1204?autostart=false
and spends 5k a month on his internet access.
--
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next reply other threads:[~2015-08-12 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 16:36 Dave Taht [this message]
2015-08-14 7:30 ` jb
2015-08-14 8:28 ` Richard Mortimer
2015-08-14 14:29 ` jb
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6VEZ7=RKiYREmgs=77PfGH0Ai2g1XqQ6=ie4mP32273g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox