General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Arshan Khanifar <arshankhanifar@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Comparing bufferbloat tests (was: We built a new bufferbloat test and keen for feedback)
Date: Sun, 8 Nov 2020 17:07:55 -0500	[thread overview]
Message-ID: <6315456F-AB57-4FDB-9D26-8AA2BB0DF687@gmail.com> (raw)
In-Reply-To: <87h7q3solo.fsf@toke.dk>

Hello Toke!

> Curious to know why you picked this instead of, say, something from
> speed.cloudflare.com (since you're using that for the speed tests anyway)?

The reason we chose the static file instead of cloudflare was because the ping to Cloudflare from where I am reported a pretty high number (around 20ms), and we also noticed that there was an issue with the network path to cloudflare in general. We were getting some packet losses when doing a normal ping, and there were some latency spikes that would happen regularly. 

> Yeah, allowing some ramp-up time before determining the bandwidth seems
> reasonable, but it's not generally possible to just pick a static number
> of (say) seconds to chop off... Having the graph over time helps
> sanity-check things, though.

Yeah it’d be useful to have a real-time graph. 

> Also, a continuous graph of latency samples over time (for the whole
> duration, including idle/upload/download) is usually very instructive
> when plotting such a test.

I had that in the earlier version of the test that I sent to you previously. It would make the test look a bit complicated though, so we should maybe have an advanced view, where the user can see these charts.

> The test at speed.cloudflare.com does seem to plot real-time upload
> bandwidth; is that a privileged operation for themselves, or something?

It’s not “that” real time, they start from a small upload size, and progressively increase the file size. They will calculate the average bandwidth for each upload and show it on the chart that they have. I want to have the test continuously do a big upload, and have real-time measurements.

> If you're reporting standard deviation, I'd just label it as such. One
> good definition for jitter is IPDV:
> https://en.wikipedia.org/wiki/Packet_delay_variation

Thanks! This is great! 

> 
>> @Toke Høiland-Jørgensen
>>> Also, what are the shields below the grade supposed to mean? Do they
>>> change depending on the result? On which criteria? 
> 
> Right, cool; explaining this on the page might be useful ;)

Yeah we’ll change the texts and add more explanations in the end. 

> Just having the test be on a separate (static) page would be the obvious
> fix ;)

Correct hahah. I’ll bring that up with the team. 

Thank you so much for all the help!

Arshan

  parent reply	other threads:[~2020-11-08 22:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 21:30 [Bloat] We built a new bufferbloat test and keen for feedback Sam Westwood
2020-11-04 23:43 ` Michael Richardson
2020-11-04 23:54 ` Toke Høiland-Jørgensen
2020-11-05  1:52   ` Y
2020-11-05  0:23 ` Dave Collier-Brown
2020-11-05 11:48   ` Toke Høiland-Jørgensen
2020-11-05 13:24     ` [Bloat] Comparing bufferbloat tests (was: We built a new bufferbloat test and keen for feedback) Dave Collier-Brown
2020-11-05 14:24       ` Toke Høiland-Jørgensen
2020-11-05 16:06         ` Arshan Khanifar
2020-11-05 17:25           ` Toke Høiland-Jørgensen
2020-11-06 16:03             ` Stephen Hemminger
2020-11-06 16:17               ` Toke Høiland-Jørgensen
2020-11-06 17:05                 ` Sebastian Moeller
2020-11-08 22:07             ` Arshan Khanifar [this message]
2020-11-14  3:37               ` Dave Taht
2020-11-14 23:14                 ` Michael Richardson
2020-11-05  8:21 ` [Bloat] We built a new bufferbloat test and keen for feedback Sebastian Moeller
2020-11-05 21:30 ` Sam

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=6315456F-AB57-4FDB-9D26-8AA2BB0DF687@gmail.com \
    --to=arshankhanifar@gmail.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