Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Luca Muscariello <luca.muscariello@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: dpreed@reed.com,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat]  DC behaviors today
Date: Tue, 12 Dec 2017 15:09:36 -0000	[thread overview]
Message-ID: <CAHx=1M4tq2U8ehpU8BQ94f-VAXbh00b7k0iiwaZEDmbEgL=2kg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1712080800440.8884@uplift.swm.pp.se>

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

I think everything is about response time, even throughput.

If we compare the time to transmit a single packet from A to B, including
propagation delay, transmission delay and queuing delay,
to the time to move a much larger amount of data from A to B we use
throughput in this second case because it is a normalized
quantity w.r.t. response time (bytes over delivery time). For a single
transmission we tend to use latency.
But in the end response time is what matters.

Also, even instantaneous throughput is well defined only for a time scale
which has to be much larger than the min RTT (propagation +  transmission
delays)
Agree also that looking at video, latency and latency budgets are better
quantities than throughput. At least more accurate.










On Fri, Dec 8, 2017 at 8:05 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> On Mon, 4 Dec 2017, dpreed@reed.com wrote:
>
> I suggest we stop talking about throughput, which has been the mistaken
>> idea about networking for 30-40 years.
>>
>
> We need to talk both about latency and speed. Yes, speed is talked about
> too much (relative to RTT), but it's not irrelevant.
>
> Speed of light in fiber means RTT is approx 1ms per 100km, so from
> Stockholm to SFO my RTT is never going to be significantly below 85ms
> (8625km great circle). It's current twice that.
>
> So we just have to accept that some services will never be deliverable
> across the wider Internet, but have to be deployed closer to the customer
> (as per your examples, some need 1ms RTT to work well), and we need lower
> access latency and lower queuing delay. So yes, agreed.
>
> However, I am not going to concede that speed is "mistaken idea about
> networking". No amount of smarter queuing is going to fix the problem if I
> don't have enough throughput available to me that I need for my application.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

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

  reply	other threads:[~2017-12-12 15:09 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 17:44 [Cerowrt-devel] quad core arm Dave Taht
2017-12-03 18:18 ` Joel Wirāmu Pauling
2017-12-03 19:18 ` Matt Taggart
2017-12-03 19:55   ` Dave Taht
2017-12-03 20:47     ` Joel Wirāmu Pauling
2017-12-04  4:19       ` [Cerowrt-devel] DC behaviors today Dave Taht
2017-12-04  9:13         ` Mikael Abrahamsson
2017-12-04  9:31           ` Joel Wirāmu Pauling
2017-12-04 10:18             ` Mikael Abrahamsson
2017-12-04 10:27               ` Joel Wirāmu Pauling
2017-12-04 10:43                 ` [Cerowrt-devel] [Bloat] " Pedro Tumusok
2017-12-04 10:47                   ` Joel Wirāmu Pauling
2017-12-04 10:57                     ` Pedro Tumusok
2017-12-04 10:59                       ` Joel Wirāmu Pauling
2017-12-04 12:44                       ` Mikael Abrahamsson
2017-12-04 19:59                         ` dpreed
2017-12-08  7:05                           ` Mikael Abrahamsson
2017-12-12 15:09                             ` Luca Muscariello [this message]
2017-12-12 18:36                               ` Dave Taht
2017-12-12 22:53                                 ` dpreed
2017-12-12 23:20                                   ` Jonathan Morton
2017-12-13 10:20                                     ` Mikael Abrahamsson
2017-12-13 10:45                                   ` Luca Muscariello
2017-12-13 15:26                                   ` Neil Davies
2017-12-13 16:41                                     ` Jonathan Morton
2017-12-13 18:08                                       ` dpreed
2017-12-13 19:55                                         ` Neil Davies
2017-12-13 21:06                                           ` Jonathan Morton
2017-12-14  8:22                                       ` Mikael Abrahamsson
2017-12-17 21:37                                         ` Benjamin Cronce
2017-12-18  8:11                                           ` Mikael Abrahamsson
2017-12-17 11:52                                 ` Matthias Tafelmeier
2017-12-18  7:50                                   ` Mikael Abrahamsson
2017-12-19 17:55                                     ` Matthias Tafelmeier
2017-12-27 15:15                                       ` Matthias Tafelmeier
2018-01-20 11:55                                 ` Joel Wirāmu Pauling
2017-12-04 12:41                 ` [Cerowrt-devel] " Mikael Abrahamsson
2017-12-04 10:56         ` [Cerowrt-devel] Linux network is damn fast, need more use XDP (Was: [Bloat] DC behaviors today) Jesper Dangaard Brouer
2017-12-04 17:00           ` [Cerowrt-devel] [Bloat] Linux network is damn fast, need more use XDP (Was: " Dave Taht
2017-12-04 20:49             ` Joel Wirāmu Pauling
2017-12-07  8:43             ` Jesper Dangaard Brouer
2017-12-07  8:49             ` Jesper Dangaard Brouer
2017-12-04 17:19           ` Matthias Tafelmeier
2017-12-03 19:49 ` [Cerowrt-devel] quad core arm Dave Taht
2017-12-04  0:19   ` Michael Richardson
2017-12-04 23:18   ` Matt Taggart
2017-12-04  0:11 ` Michael Richardson
2017-12-04  0:34   ` Joel Wirāmu Pauling
2017-12-04 23:40 ` Matt Taggart
2017-12-04 23:58   ` Joel Wirāmu Pauling
2017-12-05 10:13   ` Toke Høiland-Jørgensen
2017-12-06  8:59     ` 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/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='CAHx=1M4tq2U8ehpU8BQ94f-VAXbh00b7k0iiwaZEDmbEgL=2kg@mail.gmail.com' \
    --to=luca.muscariello@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.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