From: David Lang <david@lang.hm>
To: sahil grover <sahilgrover013@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Realtime Response Under Load (RRUL) Test
Date: Sat, 18 Apr 2015 13:25:04 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1504181318530.26044@nftneq.ynat.uz> (raw)
In-Reply-To: <CADnS-2h5PTESZzn2kdGcmGyxL-d0XU9RpramA7AO0X8sNj22xg@mail.gmail.com>
[-- Attachment #1: Type: TEXT/Plain, Size: 1198 bytes --]
On Fri, 17 Apr 2015, sahil grover wrote:
> Anyone please tell me what are requirements for taking this test:
>
> 1) About Operating System :
>
> which os is best- windows or ubuntu?
> can i use windows?
whatever you are running
> 2) can i test it on home network for bufferbloat?
> or should i look for some wider network?
what are you trying to test? usually you don't get much value in testing a
when you go through
a router that is a bottleneck. so testing from one machine on your network to
another machine on your network isn't going to find anything
> 3) Any other link explaining about its procedure from scratch because i am
> newbie to all this.
It boils down to
1. do a latency test with no other load ( ping works )
2. start a large upload and see what happens to latency during the upload
3. start a large download and see what happens to latency during the download
4. start an upload and download and see what happens to latency.
the netperf test does this by having you run a netperf server on one system (on
the other side of the router that is your bottleneck), then run the test from
a machne on your network, and it does allt he steps above for you.
David Lang
[-- Attachment #2: Type: TEXT/PLAIN, Size: 140 bytes --]
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2015-04-18 20:25 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 [this message]
[not found] ` <CADnS-2j_UbD7OGYPWe2j010NgMKuyCpG8taL4qkhu3TcDdGxNA@mail.gmail.com>
2015-04-20 15:45 ` David Lang
2015-04-20 17:15 ` sahil grover
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=alpine.DEB.2.02.1504181318530.26044@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=sahilgrover013@gmail.com \
/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