From: David Collier-Brown <davec-b@rogers.com>
To: Jonathan Morton <chromatix99@gmail.com>, davecb@spamcop.net
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] How to "sell" improvement
Date: Mon, 28 Nov 2016 14:42:12 -0500 [thread overview]
Message-ID: <ce7b3d59-c597-ffab-74f0-1ed2e0d7222b@rogers.com> (raw)
In-Reply-To: <499965DD-26DF-42A2-B79A-95109C13C950@gmail.com>
On 28/11/16 02:26 PM, Jonathan Morton wrote:
>> On 28 Nov, 2016, at 20:37, David Collier-Brown <davec-b@rogers.com> wrote:
>>
>> 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"
> This is a useful set of definitions, though I would quibble that “transfer time” should also be measured from the request, not from the first response.
Latency + Transfer Time add up to make "Response Time", which is from
very beginning to very end, as you note.
>
> A more complete picture would add a measure of application-induced delay, which is visible to the user but not necessarily to the network. It is influenced mainly by the end host's performance, not by anything in the network, and would presumably count as part of the “think time” for many applications. Hence it’s not relevant for *our* objectives, but might be to others.
The response also breaks down into queue delay and service time, which
don't line up with the latency/transfer split. Service time is the time
a warm system takes to process one request-response pair, while delay is
the time spent waiting for the cache to load, stuff get read from disk
and, especially especially, the time sitting in the run-queue, twiddling
your thumbs, waiting for a CPU.
Those aren't easily measured from outside the system, although I've
approximated them with a stepping load test. They're easy to measure
in-app, though.
>
> Incidentally, did anyone notice that Intel revived their old “optimised for the Internet” marketing fluff for their new Kaby Lake CPUs? Last seen for the Pentium III, and just as disingenuous.
>
> - Jonathan Morton
>
>
"Intel inside" is a warning label (;-))
--dave
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
prev parent reply other threads:[~2016-11-28 19:42 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
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 [this message]
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=ce7b3d59-c597-ffab-74f0-1ed2e0d7222b@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=davecb@spamcop.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