General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Neil Davies <neil.davies@pnsol.com>
To: Paolo Valente <paolo.valente@unimore.it>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Detecting bufferbloat from outside a node
Date: Mon, 27 Apr 2015 11:26:16 +0100	[thread overview]
Message-ID: <30560030-8A86-481D-A310-B3B72C26C368@pnsol.com> (raw)
In-Reply-To: <3DC1A2EA-6DDD-4FF9-AD12-BB509EFB96B8@unimore.it>

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

Paolo

You are asking about the epistemology! Good start. The only things you can “know” outside the node are the things you can observe. You can infer, from the characteristics of the observations, conformance to some avowed model of behaviour.

Welcome to the world operational, denotational and intentional semantics as it relates to network performance!

Neil

On 27 Apr 2015, at 11:19, Paolo Valente <paolo.valente@unimore.it> wrote:

> 
> Il giorno 27/apr/2015, alle ore 12:10, Paolo Valente <paolo.valente@unimore.it> ha scritto:
> 
>> 
>> Il giorno 27/apr/2015, alle ore 11:57, Toke Høiland-Jørgensen <toke@toke.dk> ha scritto:
>> 
>>> Paolo Valente <paolo.valente@unimore.it> writes:
>>> 
>>>> a network-monitoring company got curious about bufferbloat issues and
>>>> asked me to investigate a little bit the following issue (quite
>>>> interesting in my opinion). Is it possible to detect, from outside a
>>>> node, if the node is bufferbloated? In particular, the only action
>>>> allowed would be to observe the packets entering and leaving the node
>>>> (plus, of course, their timing).
>>> 
>>> Sure. Just measure the timing when the network is unloaded and compare
>>> it to when it is loaded to capacity. We do that all the time.
>>> 
>>> The details of course depend on what you define by a 'node', what role
>>> it plays in the network (does it forward or originate packets?), and
>>> what control you have over the traffic flowing through it. :)
>>> 
>> 
>> Let us consider, for example, a host with a VoIP call and a large-file transfer in progress. My concern is: from inside the host, we can measure the delays experienced by the VoIP application, but, form outside, how can we detect that the application is experiencing a high latency, or, indirectly, that there is bufferbloat and hence that the application is likely to be experiencing a high latency? (Of course, I am also about to read the documents suggested by Neil.)
>> 
> 
> I am sorry, but I realized that what I said was incomplete. The main cause of my concern is that, from outside the node, we do not know whether a VoIP packet departs ad a given time because the application wants it to be sent at that time or because it has waited in the buffer for a lot of time. Similarly, we do not know how long the VoIP application will wait before getting its incoming packets delivered.
> 
> Of course, if a bufferbloated state can be measured by other external measurements, then we can infer the problem indirectly.
> 
> Are there flaws in my above considerations?
> 
> Thanks,
> Paolo
> 
>> Thanks,
>> Paolo
>> 
>>> -Toke
>> 
>> 
>> --
>> Paolo Valente                                                 
>> Algogroup
>> Dipartimento di Fisica, Informatica e Matematica		
>> Via Campi, 213/B
>> 41125 Modena - Italy        				  
>> homepage:  http://algogroup.unimore.it/people/paolo/
> 
> 
> --
> Paolo Valente                                                 
> Algogroup
> Dipartimento di Fisica, Informatica e Matematica		
> Via Campi, 213/B
> 41125 Modena - Italy        				  
> homepage:  http://algogroup.unimore.it/people/paolo/
> 
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


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

  parent reply	other threads:[~2015-04-27 10:25 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  9:48 Paolo Valente
2015-04-27  9:54 ` Neil Davies
2015-04-27 10:45   ` Toke Høiland-Jørgensen
2015-04-27 10:57     ` Neil Davies
2015-04-27 14:22       ` Toke Høiland-Jørgensen
2015-04-27 20:27         ` Neil Davies
2015-04-27 15:51       ` Toke Høiland-Jørgensen
2015-04-27 20:38         ` Neil Davies
2015-04-27 21:37           ` Toke Høiland-Jørgensen
2015-04-28  7:14             ` Neil Davies
2015-04-27 11:54   ` Paolo Valente
2015-04-27 15:25     ` Jonathan Morton
2015-04-27 20:30       ` Neil Davies
2015-04-27 23:11         ` Jonathan Morton
2015-04-28  7:17           ` Neil Davies
2015-04-28  9:58             ` Sebastian Moeller
2015-04-28 10:23               ` Neil Davies
2015-05-04 10:10                 ` Paolo Valente
2015-05-04 10:21                   ` Neil Davies
2015-05-04 10:28                   ` Jonathan Morton
2015-05-04 10:41                     ` Paolo Valente
2015-05-04 10:44                       ` Neil Davies
2015-05-04 10:42                     ` Neil Davies
2015-05-04 11:33                       ` Jonathan Morton
2015-05-04 11:39                         ` Neil Davies
2015-05-04 12:17                           ` Jonathan Morton
2015-05-04 12:35                             ` Neil Davies
2015-05-04 17:39                               ` David Lang
2015-05-04 19:09                                 ` Jonathan Morton
2015-04-28 16:05             ` Rick Jones
2015-04-27 20:13     ` Neil Davies
2015-04-27  9:57 ` Toke Høiland-Jørgensen
2015-04-27 10:10   ` Paolo Valente
2015-04-27 10:19     ` Paolo Valente
2015-04-27 10:23       ` Toke Høiland-Jørgensen
2015-04-27 10:53         ` Paolo Valente
2015-04-27 20:39           ` David Lang
2015-05-04 10:31             ` Paolo Valente
2015-04-27 10:26       ` Neil Davies [this message]
2015-04-27 10:32         ` Toke Høiland-Jørgensen
2015-04-27 10:38           ` Neil Davies
2015-04-27 10:52             ` Toke Høiland-Jørgensen
2015-04-27 11:03               ` Neil Davies
2015-04-27 12:03                 ` Toke Høiland-Jørgensen
2015-04-27 20:19                   ` Neil Davies
2015-05-19 21:23                   ` Alan Jenkins

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=30560030-8A86-481D-A310-B3B72C26C368@pnsol.com \
    --to=neil.davies@pnsol.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=paolo.valente@unimore.it \
    /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