From: David Lang <david@lang.hm>
To: <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bufferbloat Paper
Date: Tue, 08 Jan 2013 21:02:05 -0800 [thread overview]
Message-ID: <12916ad96425700de4a1892ad43f90b1@lang.hm> (raw)
In-Reply-To: <20130109033920.C47B95B2B40@lawyers.icir.org>
On Tue, 08 Jan 2013 22:39:20 -0500, Mark Allman wrote:
>> > Note the paper does not work in units of *connections* in section
>> 2, but
>> > rather in terms of *RTT samples*. So, nearly 5% of the RTT
>> samples add
>> >>= 400msec to the base delay measured for the given remote (in the
>> > "residential" case).
>>
>> Hmm, yes, I was wondering about this and was unable to fully grok
>> it:
>> what, exactly, is an RTT sample? :)
>
> One RTT measurement between the CCZ monitoring point and the remote
> end
> host.
>
>> Incidentally, are the data extraction scripts available somewhere?
>> Might be worthwhile to distribute them as some kind of tool that
>> people with interesting vantage points could apply to get useful
>> data?
>
> Well, they are not readily available. I used a non-public extension
> to
> Bro (that is not mine) to get the RTT samples. So, that is a
> sticking
> point. And, then there is a ball of goop to analyze those. If folks
> have a place they can monitor and are interested in doing so, please
> contact me. I can probably get this in shape enough to give you.
> But,
> I doubt I'll be able to somehow package this for general consumption
> any
> time soon.
I really like the idea of trying to measure latency by sniffing the
network and watching the time for responses.
If this can work then I think a lot of people would be willing to put a
sniffer inline in their datacenter to measure this.
How specialized is what you are running? can it be made into a
single-use tool that just measures and reports latency?
David Lang
next prev parent reply other threads:[~2013-01-10 7:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r4lvgss4.fsf@toke.dk>
2013-01-09 3:39 ` Mark Allman
2013-01-09 5:02 ` David Lang [this message]
2013-01-18 1:23 ` grenville armitage
2013-01-17 14:03 ` [Bloat] Passive RTT measurements [was: Re: Bufferbloat Paper] Simon Leinen
2013-01-17 14:08 ` Simon Leinen
2013-01-18 23:16 ` Hagen Paul Pfeifer
2013-01-08 19:03 [Bloat] bufferbloat paper Hal Murray
2013-01-08 20:28 ` Jonathan Morton
2013-01-09 0:12 ` David Lang
2013-01-09 1:59 ` Mark Allman
2013-01-09 4:53 ` David Lang
2013-01-09 5:13 ` Jonathan Morton
2013-01-09 5:32 ` Mark Allman
-- strict thread matches above, loose matches on Subject: below --
2013-01-08 7:35 Ingemar Johansson S
2013-01-18 22:00 ` Haiqing Jiang
2013-01-07 23:37 [Bloat] Bufferbloat Paper Hagen Paul Pfeifer
2013-01-08 0:33 ` Dave Taht
2013-01-08 0:40 ` David Lang
2013-01-08 2:04 ` Mark Watson
2013-01-08 2:24 ` David Lang
2013-01-09 20:08 ` Michael Richardson
2013-01-08 4:52 ` Mark Watson
2013-01-08 1:54 ` Stephen Hemminger
2013-01-08 2:15 ` Oliver Hohlfeld
2013-01-08 12:44 ` Toke Høiland-Jørgensen
2013-01-08 13:55 ` Mark Allman
2013-01-09 0:03 ` David Lang
2013-01-10 13:01 ` Mark Allman
2013-01-09 20:14 ` Michael Richardson
2013-01-09 20:19 ` Mark Allman
2013-01-09 20:31 ` Michael Richardson
2013-01-10 18:05 ` Mark Allman
2013-01-08 14:04 ` Mark Allman
2013-01-08 17:22 ` Dave Taht
2013-01-09 20:05 ` Michael Richardson
2013-01-09 20:14 ` Mark Allman
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=12916ad96425700de4a1892ad43f90b1@lang.hm \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.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