Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
	"aqm@ietf.org" <aqm@ietf.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] [aqm] the side effects of 330ms lag in the real world
Date: Tue, 29 Apr 2014 18:51:22 +0200	[thread overview]
Message-ID: <CALQXh-M-otYhYuC+hzNDdR1pT46Ot2Rd8SPJuSKGPwwBC66KAw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw55ZzUp7BnskibMBTEfW6xouUqJARhGCNxLBCH8y6QCvQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]

On Tue, Apr 29, 2014 at 5:46 PM, Dave Taht <dave.taht@gmail.com> wrote:


> > 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.


With my DSL connection, 80% of the latency to "most" things (dns, cdns,
etc) is between the modem and dslam.  That's a place where fiber would fare
far better.  I get 20-25ms to the first router after the dsl modem, and
then akamai and google are within 3-5ms of that.

(and was that american-in-paris comment aimed at me?  ;)

La Monde is, amusingly, about 150ms from me here in Paris.  But
nytimes.comis 270-280...

And the CDN used by lamonde.fr is 60ms away.

And 20-25ms of all of that is DSL overhead.

-Aaron

[-- Attachment #2: Type: text/html, Size: 2017 bytes --]

  reply	other threads:[~2014-04-29 16:51 UTC|newest]

Thread overview: 16+ 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
2014-04-29 16:51         ` Aaron Wood [this message]
2014-04-29 16:44       ` [Cerowrt-devel] [Bloat] " 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
2014-04-29 23:01 Hal Murray

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=CALQXh-M-otYhYuC+hzNDdR1pT46Ot2Rd8SPJuSKGPwwBC66KAw@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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