Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Greg White <g.white@cablelabs.com>
Cc: "William Chan (陈智昌)" <willchan@chromium.org>,
	"aqm@ietf.org" <aqm@ietf.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [aqm] chrome web page benchmarker fixed
Date: Sat, 19 Apr 2014 12:29:05 -0700	[thread overview]
Message-ID: <CAA93jw4U5G1E_1j+MLzC4evPS6Zj0f8w2O4ORxcmoeq-PbB8cw@mail.gmail.com> (raw)
In-Reply-To: <CF76DA80.32EBC%g.white@cablelabs.com>

On Fri, Apr 18, 2014 at 1:41 PM, Greg White <g.white@cablelabs.com> wrote:
> On 4/18/14, 1:05 PM, "Dave Taht" <dave.taht@gmail.com> wrote:
>
>>On Fri, Apr 18, 2014 at 11:15 AM, Greg White <g.white@cablelabs.com>
>>wrote:
>>>
>>> The choice of RTTs also came from the web traffic captures. I saw
>>> RTTmin=16ms, RTTmean=53.8ms, RTTmax=134ms.
>>
>>Get a median?
>
> Median value was 62ms.
>
>>
>>My own stats are probably quite skewed lower from being in california,
>>and doing some tests from places like isc.org in redwood city, which
>>is insanely well
>>co-located.
>
> Mine are probably skewed too. I was told that global median (at the time I
> collected this data) was around 100ms.

Well, the future is already here, just not evenly distributed. Nearly every
sample I'd taken at the same time as from, almost entirely from major
cities, came in at under 70ms median.

It strikes me that a possibly useful metric would be object size vs RTT,
over time.

>



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

  reply	other threads:[~2014-04-19 19:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 17:49 [Cerowrt-devel] " Dave Taht
2014-04-17 19:01 ` [Cerowrt-devel] [aqm] " William Chan (陈智昌)
2014-04-17 21:07   ` Dave Taht
2014-04-17 22:29     ` William Chan (陈智昌)
2014-04-18 18:15     ` Greg White
2014-04-18 18:48       ` dpreed
2014-04-18 19:27         ` Greg White
2014-04-18 19:05       ` Dave Taht
2014-04-18 19:40         ` Dave Taht
2014-04-18 20:41         ` Greg White
2014-04-19 19:29           ` Dave Taht [this message]
2014-04-30 14:09             ` Dave Taht

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw4U5G1E_1j+MLzC4evPS6Zj0f8w2O4ORxcmoeq-PbB8cw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=g.white@cablelabs.com \
    --cc=willchan@chromium.org \
    /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