General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: sahil grover <sahilgrover013@gmail.com>
To: David Lang <david@lang.hm>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Realtime Response Under Load (RRUL) Test
Date: Mon, 20 Apr 2015 22:45:41 +0530	[thread overview]
Message-ID: <CADnS-2i290vXQ5PFxNDmmkkC7Rr0aCkK0KnShXe-XbNTSKOLeQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1504200842080.12399@nftneq.ynat.uz>

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

>Contact me off-list if you want a deeper discussion of the history of
bufferbloat and what's going on to try and solve it.

Sure, i will. You made my day  :)
because by reading papers/articles, i didn't get that i gained from you
people.
Infact always wanna hear something like this.

So Thanks a lot for being so kind.


On Mon, Apr 20, 2015 at 9:15 PM, David Lang <david@lang.hm> wrote:

> On Mon, 20 Apr 2015, sahil grover wrote:
>
>  David Sir,
>>
>> Thanks for answering.
>>
>> can you please tell me how to interpret its output?
>>
>> By   "netperf-wrapper rrul netperf.bufferbloat.net" ( i chose netserver
>> that is running on netperf.bufferbloat.net)
>> output(result.png) is attached.
>>
>> please tell me first what does it say generally?
>> secondly,  anything related with bufferbloat point of view.
>>
>
> latency should not increase significantly under load. The fact that it
> does indicates that you have a problem. The fact that the latency can
> increase to multi-second values for many people indicates a big problem.
>
> take a look at the new test that's available at
> https://www.dslreports.com/speedtest and then look at the results tab and
> see how the latency increases during the download and upload tests.
>
> If you have a system without excessive buffering, you would not see
> massive increases in latency.
>
> Contact me off-list if you want a deeper discussion of the history of
> bufferbloat and what's going on to try and solve it.
>
> David Lang
>

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

      reply	other threads:[~2015-04-20 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17  5:18 sahil grover
2015-04-18 20:25 ` David Lang
     [not found]   ` <CADnS-2j_UbD7OGYPWe2j010NgMKuyCpG8taL4qkhu3TcDdGxNA@mail.gmail.com>
2015-04-20 15:45     ` David Lang
2015-04-20 17:15       ` sahil grover [this message]

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=CADnS-2i290vXQ5PFxNDmmkkC7Rr0aCkK0KnShXe-XbNTSKOLeQ@mail.gmail.com \
    --to=sahilgrover013@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=david@lang.hm \
    /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