From: Sebastian Moeller <sebastian.moeller@gmail.com>
To: flent-users <flent-users@flent.org>
Subject: [Flent-users] Saturating test with configurable packet-size/MSS?
Date: Fri, 3 May 2019 10:09:04 +0200 [thread overview]
Message-ID: <219CDCB8-9691-4E6B-B999-1F9AA145FD08@gmail.com> (raw)
Dear all,
Loganaden remined me of a pet project of mine, deducing the per-packet-overhead from non ATM/AAL5 carriers. Now, I believe I have an approach that might be worth exploring*, but that requires me to saturate my link with packets of different packet sizes. so I wonder is there an easy way inside flent to run a fully saturating TCP or UDP test (multiple flows required to saturate the link are fine) and have control over packetsize from within flent/the specific flent test?
Best Regards
Sebastian
*) In theory it works but my current approach absolutely requires me to measure the maximum goodput to >= 99.8% correct, which is another challenge in itself ;) The catch is that on a given link both gross-rate and per-packet-overhead are unkown and goodput can only be estimated making the whole endeavor slightly tricky...
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
reply other threads:[~2019-05-03 9:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=219CDCB8-9691-4E6B-B999-1F9AA145FD08@gmail.com \
--to=sebastian.moeller@gmail.com \
--cc=flent-users@flent.org \
/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