From: Jonathan Morton <chromatix99@gmail.com>
To: rick.jones2@hp.com
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Measuring latency-under-load consistently
Date: Sat, 12 Mar 2011 03:44:05 +0200 [thread overview]
Message-ID: <0E7F16C4-58DA-43FE-AB84-A3BCBBB6D905@gmail.com> (raw)
In-Reply-To: <1299892197.2087.2061.camel@tardy>
On 12 Mar, 2011, at 3:09 am, Rick Jones wrote:
>>> You may be able to get most of what you want with a top-of-trunk netperf
>>> "burst mode" TCP_RR test. It isn't quite an exact match though.
>>
>> I don't really see how that would get the measurement I want.
>
> Then one TCP_STREAM (or TCP_MAERTS) and one TCP_RR with all the RTT
> stats and histogram enabled :)
Closer, but that doesn't seem to be self-tuning - and often one bulk flow doesn't fill the pipe any more.
I want to scale up to FTTH and GigE, and down to V.34bis and GPRS - all of which are (still) relevant network technologies today - without any error-prone parameters to enter except the identity of the server.
Ideally it should be robust enough for use by random ISP technicians, regulatory officials and end-users, and the output should be accordingly simple to interpret.
So yes, code reuse is great, but only if it does what I need it to. I need the practice anyway. :-)
- Jonathan
next prev parent reply other threads:[~2011-03-12 1:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 0:00 Jonathan Morton
2011-03-12 0:13 ` Rick Jones
2011-03-12 0:45 ` Jonathan Morton
2011-03-12 1:09 ` Rick Jones
2011-03-12 1:44 ` Jonathan Morton [this message]
2011-03-12 3:19 ` richard
2011-03-12 3:52 ` Jonathan Morton
2011-03-12 4:04 ` richard
2011-03-12 21:57 ` Jonathan Morton
2011-03-12 22:23 ` richard
2011-03-12 23:58 ` Jonathan Morton
2011-03-12 22:21 ` Fred Baker
2011-03-12 23:03 ` Jonathan Morton
2011-03-13 6:54 ` Fred Baker
2011-03-13 14:24 ` 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/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=0E7F16C4-58DA-43FE-AB84-A3BCBBB6D905@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=rick.jones2@hp.com \
/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