CoDel AQM discussions
 help / color / mirror / Atom feed
From: sahil grover <sahilgrover013@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] RRUL Test
Date: Tue, 21 Apr 2015 21:05:59 +0530	[thread overview]
Message-ID: <CADnS-2hK94dVK=OLPtruAVu9RivcthNsJmEfHuXs3PY4qi7JHQ@mail.gmail.com> (raw)
In-Reply-To: <CADnS-2irYpcTSp-XN6Nqo3wjZYwGSWPCjV6nVtTU8mrTVZorog@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3855 bytes --]

yeah  with wired network it works:

1)  netperf-wrapper rrul netperf.bufferbloat.net

Test data is in ./rrul-2015-04-21T204050.322476.json.gz (use with -i to
format)

and output is result2.png(is attached).

2)  netperf-wrapper rrul -p all_scaled -l 60 -H netperf.bufferbloat.net

Graph(result3.png) is made.
But it does not tell anything at terminal(Like in 1st case Test data is
in....... or command never stops)
Seems like it keeps running.
Is it normal?


Also wanna know about what could be issue with my wifi?



On Tue, Apr 21, 2015 at 8:21 PM, sahil grover <sahilgrover013@gmail.com>
wrote:

> No,Firewall is disabled.
>
> tried with wired network
>
> 1. netperf -D -0.20 -H netperf.bufferbloat.net -t TCP_STREAM
>
> MIGRATED TCP STREAM TEST from 0.0.0.0 () port 0 AF_INET to
> atl.richb-hanover.com () port 0 AF_INET : demo
> Interim result:    0.40 10^6bits/s over 0.324 seconds ending at
> 1429627638.283
> Interim result:    0.28 10^6bits/s over 0.462 seconds ending at
> 1429627638.745
> Interim result:    1.61 10^6bits/s over 0.244 seconds ending at
> 1429627638.989
> Interim result:    0.98 10^6bits/s over 0.401 seconds ending at
> 1429627639.390
> Interim result:    0.51 10^6bits/s over 1.034 seconds ending at
> 1429627640.424
> Interim result:    0.44 10^6bits/s over 1.491 seconds ending at
> 1429627641.914
> Interim result:    0.27 10^6bits/s over 2.418 seconds ending at
> 1429627644.333
> Interim result:    0.70 10^6bits/s over 1.308 seconds ending at
> 1429627645.641
> Interim result:    0.49 10^6bits/s over 1.334 seconds ending at
> 1429627646.975
> Interim result:    0.40 10^6bits/s over 0.984 seconds ending at
> 1429627647.959
> Recv   Send    Send
> Socket Socket  Message  Elapsed
> Size   Size    Size     Time     Throughput
> bytes  bytes   bytes    secs.    10^6bits/sec
>
> 174760  16384  16384    13.07       0.38
>
>
>
>
> 2.  netperf -D -0.20 -H netperf-eu.bufferbloat.net -t TCP_STREAM
>
>
> MIGRATED TCP STREAM TEST from 0.0.0.0 () port 0 AF_INET to kau.toke.dk ()
> port 0 AF_INET : demo
> Interim result:    0.53 10^6bits/s over 0.247 seconds ending at
> 1429627754.173
> Interim result:    0.30 10^6bits/s over 0.437 seconds ending at
> 1429627754.610
> Interim result:    1.70 10^6bits/s over 0.462 seconds ending at
> 1429627755.072
> Interim result:    1.24 10^6bits/s over 0.424 seconds ending at
> 1429627755.496
> Interim result:    0.48 10^6bits/s over 1.378 seconds ending at
> 1429627756.874
> Interim result:    0.39 10^6bits/s over 2.686 seconds ending at
> 1429627759.560
> Interim result:    0.47 10^6bits/s over 2.215 seconds ending at
> 1429627761.775
> Interim result:    0.43 10^6bits/s over 2.151 seconds ending at
> 1429627763.926
> Recv   Send    Send
> Socket Socket  Message  Elapsed
> Size   Size    Size     Time     Throughput
> bytes  bytes   bytes    secs.    10^6bits/sec
>
>  87380  16384  16384    12.81       0.42
>
>
>
>
>
> On Tue, Apr 21, 2015 at 7:00 PM, Toke Høiland-Jørgensen <toke@toke.dk>
> wrote:
>
>> sahil grover <sahilgrover013@gmail.com> writes:
>>
>> > netperf -D -0.20 -H netperf-eu.bufferbloat.net -t TCP_STREAM
>> >
>> > Shows:
>> >
>> > MIGRATED TCP STREAM TEST from 0.0.0.0 () port 0 AF_INET to kau.toke.dk
>> () port 0
>> > AF_INET : demo
>> > Recv Send Send
>> > Socket Socket Message Elapsed
>> > Size Size Size Time Throughput
>> > bytes bytes bytes secs. 10^6bits/sec
>> >
>> > 87380 16384 16384 14.00 0.00
>>
>> Right, so there's definitely something messing with the outgoing
>> traffic. I have no idea what could cause netperf to only be able to send
>> traffic in one direction (perhaps Rick knows?). Do you have any sort of
>> firewall between you and the internet that might interfere with traffic?
>>
>> -Toke
>>
>
>

[-- Attachment #1.2: Type: text/html, Size: 8928 bytes --]

[-- Attachment #2: result2.png --]
[-- Type: image/png, Size: 123420 bytes --]

[-- Attachment #3: result3.png --]
[-- Type: image/png, Size: 117463 bytes --]

  reply	other threads:[~2015-04-21 15:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17  5:22 sahil grover
2015-04-17  6:48 ` Andrew McGregor
2015-04-17  9:04   ` sahil grover
2015-04-17 11:15     ` Andrew McGregor
2015-04-17 12:42     ` Toke Høiland-Jørgensen
2015-04-17 14:52       ` sahil grover
2015-04-17 15:49         ` sahil grover
2015-04-17 16:25           ` Rick Jones
2015-04-18 12:42             ` Toke Høiland-Jørgensen
2015-04-20 12:05               ` sahil grover
2015-04-20 15:26                 ` Toke Høiland-Jørgensen
2015-04-20 15:43                   ` sahil grover
2015-04-21  8:57                     ` Toke Høiland-Jørgensen
2015-04-21  9:57                       ` sahil grover
2015-04-21 13:30                         ` Toke Høiland-Jørgensen
2015-04-21 14:51                           ` sahil grover
2015-04-21 15:35                             ` sahil grover [this message]
2015-04-21 16:19                               ` sahil grover
2015-04-21 19:19                                 ` Jonathan Morton
2015-04-21 16:07                           ` Rick Jones
2015-04-17 16:56         ` Jonathan Morton

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/codel.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-2hK94dVK=OLPtruAVu9RivcthNsJmEfHuXs3PY4qi7JHQ@mail.gmail.com' \
    --to=sahilgrover013@gmail.com \
    --cc=codel@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