* [Flent-users] Saturating test with configurable packet-size/MSS?
@ 2019-05-03 8:09 Sebastian Moeller
0 siblings, 0 replies; only message in thread
From: Sebastian Moeller @ 2019-05-03 8:09 UTC (permalink / raw)
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?
*) 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-05-03 9:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-03 8:09 [Flent-users] Saturating test with configurable packet-size/MSS? Sebastian Moeller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox