General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Neil Davies <neil.davies@pnsol.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Detecting bufferbloat from outside a node
Date: Mon, 27 Apr 2015 21:27:19 +0100	[thread overview]
Message-ID: <8A4A25B0-B7B5-47C6-9CD1-AD744F3C24FB@pnsol.com> (raw)
In-Reply-To: <87d22p1wim.fsf@toke.dk>

Toke


On 27 Apr 2015, at 15:22, Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> Neil Davies <neil.davies@pnsol.com> writes:
> 
>> You'll find the way that ∆Q can be decomposed into basis set of ∆Q|G,
>> ∆Q|S and ∆Q|V - helps work out which parts of the budget get eaten up
>> by different elements of the network design/architecture.
> 
> Right, I got that part. What I'm missing is how you define the actual
> measure for ∆Q -- but that is application dependent? E.g. for web sites
> it might be load time, for VoIP it might be MOS score?
> 
> -Toke


For VoIP the aspects of ∆Q that are of interest (after the total one way delay) are the 
delay variance and loss rate - take a look at https://ivanovic.web.cern.ch/ivanovic/articles/open-2004-007.pdf 
(which is the tech report behind what was published in SPECTS'03 (Beuran, R., Ivanovici, M., Dobinson,
 B., Davies, N., Thompson, P.: Network Quality of Service Measurement System for
Application Requirements Evaluation)

In other aspects it might be "time to first frame" (VoD) or "possibility of a buffer starvation event per operating hour" (VoD)
the QoE (Qualty of Experience) metric needs to be one that has a relationship with the users' perception.]

Neil

  reply	other threads:[~2015-04-27 20:27 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 [this message]
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
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=8A4A25B0-B7B5-47C6-9CD1-AD744F3C24FB@pnsol.com \
    --to=neil.davies@pnsol.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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