From: Pete Heist <pete@eventide.io>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: flent-users <flent-users@flent.org>
Subject: Re: [Flent-users] irtt packet-cluster mode for estimating queueing delay
Date: Mon, 7 May 2018 08:40:21 +0200 [thread overview]
Message-ID: <3F7CBBF7-5C10-4015-B634-383D7787520C@eventide.io> (raw)
In-Reply-To: <731C3150-7935-4CE2-B169-CF1637B9A94A@gmx.de>
> On May 6, 2018, at 9:17 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
>
> you could also try different packet sizes for you probes. The size ratio should give you an idea about the RTT difference explained by simple transit times and anything on top of that might be related to queueing. I am probably severely underestimating the scope of your question, but I believe that that also has the advantage that, unlike packet-tuples, will not be as sensitive to bonded path segments (which probably do not exist in your environment in the first place).
I was also considering adding the option to irtt for different packet sizes in each cluster. I’d have to change the IPDV calculation to only calculate it for like-sized packets, which is possible.
I see how using the RTTs for different packet lengths might help estimate the transmission time, but not how I could use that to differentiate between channel contention and queueing delays(?) Maybe I see what you’re saying, that in addition to varying the DSCP value, I can also vary length to estimate the transmission time, and subtract that from the estimate I get for “contention” to have a better approximation of how much contention time there is, which sounds like a good idea... :)
I don’t know of any bonded segments in this case…
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
parent reply other threads:[~2018-05-07 6:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <731C3150-7935-4CE2-B169-CF1637B9A94A@gmx.de>]
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.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F7CBBF7-5C10-4015-B634-383D7787520C@eventide.io \
--to=pete@eventide.io \
--cc=flent-users@flent.org \
--cc=moeller0@gmx.de \
--subject='Re: [Flent-users] irtt packet-cluster mode for estimating queueing delay' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox