From: Dave Taht <dave.taht@gmail.com>
To: Hal Murray <hmurray@megapathdsl.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] backbone loss statistics over the past 15 years or so?
Date: Fri, 19 Jun 2015 09:28:32 -0700 [thread overview]
Message-ID: <CAA93jw756Z4AgDocEZW7_tcxBWtKhN-V2y4DRW6VOC+UGpkg3Q@mail.gmail.com> (raw)
In-Reply-To: <20150618193233.DC547406057@ip-64-139-1-69.sjc.megapath.net>
On Thu, Jun 18, 2015 at 12:32 PM, Hal Murray <hmurray@megapathdsl.net> wrote:
>
> I don't think you can measure backbone loss using ping unless you control both ends and ensure that both last-miles are not contributing to the problem.
Well, fractional percentages would be nice to have out of this website.
I have a great title for a paper one day: "Bufferbloat and the Rise of
the Too-Perfect Network".
>
> I think there are several different areas to investigate. The main one is whether your packet gets handed off between two "backbone" IPSs that are currently squabbling about who is going to pay whom how much. The obvious example is Netflix vs Comcast.
The MIT paper was awesome...
But I am thinking that supply (on downlinks) is outstripping demand,
along the first world edge, now... it really is hard to imagine how
much more bandwidth one can consume...
> I don't have any numbers, but I think over the past 5 or 10 years, all the major ISPs have set things up so that all their internal links are overprovisioned. You might notice packet loss when a link goes down and the traffic patterns get rearranged. (I know you can see changes in transit time using NTP.)
>
> I have an old/slow DLS link. I get close to 0% packet loss if my last mile is not busy and lots of loss when it is overloaded.
>
> --
> These are my opinions. I hate spam.
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
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 prev parent reply other threads:[~2015-06-19 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 19:32 Hal Murray
2015-06-19 16:28 ` Dave Taht [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-17 19:10 Dave Taht
2015-06-17 20:34 ` Rick Jones
2015-06-17 22:34 ` Benjamin Cronce
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=CAA93jw756Z4AgDocEZW7_tcxBWtKhN-V2y4DRW6VOC+UGpkg3Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=hmurray@megapathdsl.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