From: Benjamin Cronce <bcronce@gmail.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] backbone loss statistics over the past 15 years or so?
Date: Wed, 17 Jun 2015 17:34:32 -0500 [thread overview]
Message-ID: <CAJ_ENFE+K-7XRuz2-4Xw6YqK=RiSJf6OEK+9Jos2mFF6UFsCvA@mail.gmail.com> (raw)
In-Reply-To: <5581D9CA.40201@hp.com>
[-- Attachment #1: Type: text/plain, Size: 2542 bytes --]
> Now in 2015 I notice that it is at 0% packet loss worldwide. Looks
> > like the big boys found a way to fight any connection speed, and
> > buffer issues that where the cause of what was an ever increasing
> > packet loss issue. My wish is that it would now make it all the way
> > down to the end of the last mile. The issues with packet loss due to
> > buffer bloat that are now at the end of the home and business
> > connections I feel helps lead to the congestion issues we see during
> > the high use periods at night. "
>
> http://www.internettrafficreport.com/faq.htm#measure
>
> > Q: How do you measure "Internet traffic?"
> > A: A test called "ping" is used to measure round-trip travel time
> > along major paths on the Internet. We have several servers in
> > different areas of the globe perform the same ping at the same time.
> > Each test server then compares the current response to past responses
> > from the same test to determine if the response was bad or good on a
> > scale of 0 to 100. The scores from all test servers are averaged
> > together into a single index.
>
> If you drill-down on regions, it will show individual routers. The
> results seem to be particularly binary - a given router will have either
> an index of 100 and a loss percentage of 0, or an index of 0 and a loss
> percentage of 100. Asia seems to have a couple exceptions proving the
rule.
>
> You will probably get a kick out of:
>
> http://www.internettrafficreport.com/faq.htm#packet
Dear lord! Quote: "as long as it is under 5% or so you shouldn't even
notice".
In the long long ago, I've had issues with VoIP having issues with under 1%
loss. Issues as in perceptible differences that were both distracting and
sometimes problematic.
More of the issue is that packetloss is typically associated with
congestion which also means high ping times for most. Even then, 5% loss?!
Until recently, I've had pings running 24/7 against external servers like
Google.com, 8.8.8.8, 8.8.4.4, 4.2.2.2, etc. At some point I let ping run
for a month strait and had 0.0002% loss, two ten-thousandths of a percent,
rounded to nearest. Something like 10 packets out of 2.5mil samples that
were taken every 0.5sec. To my ISP during that same time period I had 0%
loss. At one point I let a ping run against an Amazon AWS server in both
Germany and London. Both showed about 0.01-0.001% loss over nearly a week.
Both are about an 8.5k mile round trip if by a bee-line.
>
> I'm not sure if they are setup to report fractional packet loss
percentages
[-- Attachment #2: Type: text/html, Size: 3310 bytes --]
next prev parent reply other threads:[~2015-06-17 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 19:10 Dave Taht
2015-06-17 20:34 ` Rick Jones
2015-06-17 22:34 ` Benjamin Cronce [this message]
2015-06-18 19:32 Hal Murray
2015-06-19 16:28 ` Dave Taht
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='CAJ_ENFE+K-7XRuz2-4Xw6YqK=RiSJf6OEK+9Jos2mFF6UFsCvA@mail.gmail.com' \
--to=bcronce@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=rick.jones2@hp.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