From: David Collier-Brown <davec-b@rogers.com>
To: Simon Barber <simon@superduper.net>, davecb@spamcop.net
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] How to "sell" improvement
Date: Mon, 28 Nov 2016 14:25:40 -0500 [thread overview]
Message-ID: <f688f662-1661-05cc-3f7c-e64de4b70e48@rogers.com> (raw)
In-Reply-To: <8A0CE391-C77E-4B3F-B2B0-7F9FDDB8DFCF@superduper.net>
[-- Attachment #1: Type: text/plain, Size: 5014 bytes --]
Yes, especially for
* the performance-reporting tools' own page and also for
* some well-known, moderately complex ones.
Not the minimalist Google front page, but perhaps a particular query...
--dave
On 28/11/16 01:58 PM, Simon Barber wrote:
> Web page load time.
>
> Simon
>
>> On Nov 28, 2016, at 10:37 AM, David Collier-Brown <davec-b@rogers.com> wrote:
>>
>> In this context, I'd say latency and the effect of bloat reduction on it and transfer time.
>>
>> Dave Taht can say much more (;-))
>> I'm just echoing his concern, from the point of view of a capacity planner.
>>
>> --dave c-b
>> [I'm using latency as the time from the request to the first response, transfer time as the time from the first response to the last response, which may be 0, and sleep/think time as the time from the last response to the next request, for a given stream of requests and responses, AKA "transactions"]
>>
>>
>> On 28/11/16 12:59 PM, Kathleen Nichols wrote:
>>> That's a good idea in general, but what are you measuring for your
>>> "actual performance"?
>>> Raw throughput? Goodput (which requires a bit of processing)? Then what
>>> about delay?
>>>
>>> On 11/28/16 9:41 AM, David Collier-Brown wrote:
>>>> Put the speed-test /into the router/, with a big red button to turn
>>>> fq_codel on and off.
>>>>
>>>> * The performance reporting graphs can then run on a browser page
>>>> for as long as you like, while you do other things, and go back to
>>>> the page and see what it's been like. * Have a line for "perfect"
>>>> performance, and anyone can see how close you're system is coming to
>>>> it. * Have a button for a synthetic load test, of some shortish
>>>> duration, and, * Put it on normal Linux hosts too, so you can test
>>>> end-to-end.
>>>>
>>>>
>>>> This has the advantage that it's code-first, so you don't have to
>>>> convince the uninterested, and from it you can write a small and
>>>> limited RFC to tell everyone else how you did it.
>>>>
>>>> As each new improvement comes along, actual performance slowly gets
>>>> closer and closer to the optimal performance line...
>>>>
>>>> --dave
>>>>
>>>>
>>>> On 28/11/16 10:21 AM, Jonathan Foulkes wrote:
>>>>> Thanks for the Introduction Rich, and thanks again to you and many
>>>>> others on this list for all your contributions over the years
>>>>> helping to combat bloat.
>>>>>
>>>>> This product was born of my own frustration with finding a way to
>>>>> help neighbors and family get a simple off-the-shelf solution that
>>>>> even non-technical users can deploy.
>>>>>
>>>>> I look forward to participating more actively on this list.
>>>>>
>>>>> Jonathan
>>>>>
>>>>>> On Nov 26, 2016, at 9:08 AM, Rich Brown <richb.hanover@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> I have been exchanging a few emails with Jonathan Foulkes from
>>>>>> evenroute.com. He tells me that his company is installing OpenWrt
>>>>>> on a commercial, off the shelf (COTS) TP-Link router and selling
>>>>>> them on commercially. His "secret sauce" is an auto-update
>>>>>> facility and improved setup software, which includes a
>>>>>> rate-detection step that operates continually to adjust the
>>>>>> fq_codel parameters to the actual line rate. You can take a look
>>>>>> at IQrouter.com, or look them up on Amazon.
>>>>>>
>>>>>> This might be a solution to our current conundrum about not
>>>>>> having an easy solution that solves our family's networking
>>>>>> problem. I'm going to get one of these and try it out.
>>>>>>
>>>>>> He has been following our bufferbloat and make-fifi-fast work
>>>>>> closely, as well as the work on LEDE, which he'll consider once
>>>>>> it hits a stable point. I have invited him to join this list.
>>>>>>
>>>>>> Welcome, Jonathan.
>>>>>>
>>>>>>
>>>>> _______________________________________________ Bloat mailing list
>>>>> Bloat@lists.bufferbloat.net
>>>>> https://lists.bufferbloat.net/listinfo/bloat
>>>> -- David Collier-Brown, | Always do right. This will gratify
>>>> System Programmer and Author | some people and astonish the rest
>>>> davecb@spamcop.net | -- Mark Twain
>>>>
>>>>
>>>>
>>>> _______________________________________________ Bloat mailing list
>>>> Bloat@lists.bufferbloat.net
>>>> https://lists.bufferbloat.net/listinfo/bloat
>>>>
>>> _______________________________________________
>>> Bloat mailing list
>>> Bloat@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/bloat
>>
>> --
>> David Collier-Brown, | Always do right. This will gratify
>> System Programmer and Author | some people and astonish the rest
>> davecb@spamcop.net | -- Mark Twain
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
[-- Attachment #2: Type: text/html, Size: 6743 bytes --]
next prev parent reply other threads:[~2016-11-28 19:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 14:08 [Bloat] COTS router with OpenWrt Rich Brown
2016-11-26 14:45 ` Jonathan Foulkes
2016-11-26 19:56 ` Jonathan Morton
2016-11-28 15:21 ` Jonathan Foulkes
2016-11-28 15:57 ` Dave Taht
2016-11-28 17:16 ` Jonathan Foulkes
2016-11-28 17:40 ` Toke Høiland-Jørgensen
2016-11-28 17:41 ` [Bloat] How to "sell" improvement (was: COTS router with OpenWrt) David Collier-Brown
2016-11-28 17:59 ` [Bloat] How to "sell" improvement Kathleen Nichols
2016-11-28 18:37 ` David Collier-Brown
2016-11-28 18:58 ` Simon Barber
2016-11-28 19:25 ` David Collier-Brown [this message]
2016-11-28 19:40 ` David Lang
2016-12-04 16:08 ` Jonathan Foulkes
2016-12-04 22:32 ` David Lang
2016-11-28 19:26 ` Jonathan Morton
2016-11-28 19:42 ` David Collier-Brown
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=f688f662-1661-05cc-3f7c-e64de4b70e48@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.net \
--cc=simon@superduper.net \
/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