From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat <bloat@lists.bufferbloat.net>,
"Fred Baker \(fred\)" <fred@cisco.com>,
"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 08:46:46 -0700 [thread overview]
Message-ID: <CAA93jw55ZzUp7BnskibMBTEfW6xouUqJARhGCNxLBCH8y6QCvQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1404290954460.29282@uplift.swm.pp.se>
On Tue, Apr 29, 2014 at 12:56 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Tue, 29 Apr 2014, Fred Baker (fred) wrote:
A couple points here.
1) The video went viral, and garnered over 600,000 new hits in the 12
hours since I posted
it here.
there is pent up demand for less latency. While the ad conflates
bandwidth with latency,
they could have published their RTTs on their local fiber network,
which is probably a
great deal less than dsl or cable. That counts for a lot when
accessing local services.
2) There is a lot of things an ISP can do to improve apparent latency
on the long haul
A) co-locating with a major dns server like f-root to reduce dns latency
B) co-locating with major services like google and netflix
publishing ping times to google for example might be a good tactic.
C) Better peering
>> 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:
>
>
> Yes, but as soon as you hit the long distance network the latency is the
> same regardless of access method. So while I agree that understanding the
> effect of latency is important, it's no longer a meaningful way of selling
> fiber access. If your last-mile is fiber instead of ADSL2+ won't improve
> your long distance latency.
Well, it chops a great deal from the baseline physical latency, and most
people tend to access resources closer to them than farther away. An
american in paris might want to access the NYT, but Parisians La Monde.
Similarly most major websites are replicated and use CDNs to distribute
their data closer to the user. The physical RTT matters more and more
in the last mile the more resources are co-located in the local data center.
--
Dave Täht
next prev parent reply other threads:[~2014-04-29 15:46 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)
2014-04-29 7:56 ` Mikael Abrahamsson
2014-04-29 15:46 ` Dave Taht [this message]
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=CAA93jw55ZzUp7BnskibMBTEfW6xouUqJARhGCNxLBCH8y6QCvQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=fred@cisco.com \
--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