From: "Fred Baker (fred)" <fred@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat <bloat@lists.bufferbloat.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [Cerowrt-devel] [aqm] the side effects of 330ms lag in the real world
Date: Tue, 29 Apr 2014 07:21:31 +0000 [thread overview]
Message-ID: <4130D000-FE28-4A5E-B824-3371C1602472@cisco.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1404290907240.29282@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]
On Apr 29, 2014, at 3:08 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Mon, 28 Apr 2014, Dave Taht wrote:
>
>> pretty wonderful experiment and video http://livingwithlag.com/
>
> Just so that everybody realises that this is an advertisement.
>
> Also, what access method has 300 ms access latency, let alone 3 seconds? None that I know of, the meaningful comparison would be ADSL2+ at around 25ms and 3G at around 50-100ms.
Well, we could discuss international communications. I happen to be at Infocom in Toronto, VPN’d into Cisco San Jose, and did a ping to you:
ping -c 10 swm.pp.se
PING swm.pp.se (212.247.200.143): 56 data bytes
...
--- swm.pp.se ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 249.368/342.038/456.376/71.902 ms
3 seconds is unusually high, although naval satcom is frequently in the 1.5-2.5 ms range. But I have a sample that I measured in a Dublin hotel that observed standing latencies of around 280 ms to San Jose, frequent latencies of seven seconds, and a peak of 9286 ms. Yes, the hotel DSL was horrendously misconfigured. It makes a great graphic for presentations.
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
----------------------------------------------------
The ignorance of how to use new knowledge stockpiles exponentially.
- Marshall McLuhan
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2014-04-29 7:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 1:24 [Cerowrt-devel] " Dave Taht
2014-04-29 7:08 ` [Cerowrt-devel] [aqm] " Mikael Abrahamsson
2014-04-29 7:21 ` Fred Baker (fred) [this message]
2014-04-29 7:56 ` Mikael Abrahamsson
2014-04-29 15:46 ` Dave Taht
2014-04-29 16:51 ` [Cerowrt-devel] [Bloat] " Aaron Wood
2014-04-29 16:44 ` Jim Gettys
2014-04-29 16:57 ` Jim Gettys
2014-04-29 17:01 ` [Cerowrt-devel] [aqm] [Bloat] " Toke Høiland-Jørgensen
2014-04-29 17:07 ` Jim Gettys
2014-04-29 18:09 ` Greg White
2014-04-30 3:21 ` Dave Taht
2014-04-29 17:02 ` Dave Taht
2014-04-30 6:16 ` [Cerowrt-devel] [Bloat] [aqm] " Mikael Abrahamsson
2014-04-29 7:43 ` Tristan Seligmann
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4130D000-FE28-4A5E-B824-3371C1602472@cisco.com \
--to=fred@cisco.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/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