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 21:13:29 +0100 [thread overview]
Message-ID: <E139A084-A332-4437-9591-C812C4C25067@pnsol.com> (raw)
In-Reply-To: <FE383536-AC9D-4AAB-9025-3A3A5EEB34FA@unimore.it>
Paolo
On 27 Apr 2015, at 12:54, Paolo Valente <paolo.valente@unimore.it> wrote:
> Thanks for the pointers. As for the epistemological implications of to my concerns, I must admit that I find them a little bit frightening :)
>
> After browsing some of the presentations, the relevant component for my problem seems to be the variability V. However, it is not clear to me how I can measure or infer it in my situation, i.e., if I cannot:
> 1) have any feedback on the user experience;
You'll need to consider the ∆Q|G and the ∆Q|S as well - they contribute to the overall delay and that contributes to the delivered performance. Response time to get to a certain data flow rate (say for VoD) or recovery from a packet loss (for TCP) etc interact with all the factors.
We've created models (both analytic and experimental) which relate the delivered ∆Q (all of its factors) to QoE for various apps
> 2) measure the time that elapses between when a time-sensitive application puts a message in a socket and when that message is actually sent by the node in a packet;
This is why the capture model has to be one of "timed traces" of "observables" in the TCP model the socket is one location to measure (at the two ends), the network interfaces would be another
> 3) in the opposite direction, measure the time that elapses between when a packet arrives to the node and when the application receives the message contained in the packet.
Yes, you need to view this in both directions as you need to isloate the effect of the network transport from the processing (which also has an influence on the performance)
>
> On which documents should I concentrate more to better understand this point?
>
> Thanks,
> Paolo
>
> Il giorno 27/apr/2015, alle ore 11:54, Neil Davies <neil.davies@pnsol.com> ha scritto:
>
>> Paolo
>>
>> Yes, it is - there is a whole methodology for detecting this and associated algebra for manipulation. It has been used at CERN, in various telcos and in various large scale, real time distributed systems to relate end user outcomes to the delay/loss characteristics of the network.
>>
>> Take a look at http://www.pnsol.com/publications.html, you may find http://www.pnsol.com/public/PP-PNS-2009-02.pdf as a good starting point.
>>
>> Neil
>>
>> On 27 Apr 2015, at 10:48, Paolo Valente <paolo.valente@unimore.it> wrote:
>>
>>> Hi,
>>> 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).
>>>
>>> If such a general problem is to hard or impossible to solve, do you think it is still possible at least to understand, for some type of application, if the application is experiencing a high latency because of bloated buffers inside the node? (As above, by just observing packet flows from outside the node.)
>>>
>>> Thanks,
>>> Paolo
>>>
>>> _______________________________________________
>>> Bloat mailing list
>>> Bloat@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/bloat
>>
>
>
> --
> Paolo Valente
> Algogroup
> Dipartimento di Fisica, Informatica e Matematica
> Via Campi, 213/B
> 41125 Modena - Italy
> homepage: http://algogroup.unimore.it/people/paolo/
>
next prev parent reply other threads:[~2015-04-27 20:13 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 [this message]
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
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=E139A084-A332-4437-9591-C812C4C25067@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