Täht: Flaws and features in the Flent network testing tool

Posted Jan 17, 2023 23:53 UTC (Tue) by shemminger (subscriber, #5739)
In reply to: Täht: Flaws and features in the Flent network testing tool by ballombe
Parent article: Täht: Flaws and features in the Flent network testing tool

Or maybe a future version of Flent could use something better than netperf?
Netperf seems to be widely used but had license quirks and was not maintained.

Täht: Flaws and features in the Flent network testing tool

Posted Jan 18, 2023 3:30 UTC (Wed) by mtaht (subscriber, #11087) [Link]

HP did step up and maintain it, here: https://github.com/HewlettPackard/netperf

The original author is happily retired.

Täht: Flaws and features in the Flent network testing tool

Posted Jan 19, 2023 14:04 UTC (Thu) by tohojo (subscriber, #86756) [Link] (1 responses)

It's absolutely possible to plug in a different underlying tool. We already do that for UDP RR testing (even with transparent fallback from irtt to netperf UDP_RR).

So the only problem is finding (or writing) such a tool. Know of any? I've been meaning to pick up rust, and this could be a good candidate for a project, but I'd be delighted if someone beats me to the punch :)

Täht: Flaws and features in the Flent network testing tool

Posted Jan 19, 2023 14:17 UTC (Thu) by mtaht (subscriber, #11087) [Link]

The default paradigm in the rust world seems to be to treat tcp as a request/response protocol: Open a connection, read to the end of "the file", close it, seems to be the default example, and use case. So an even better test, since we are not doing it today, would actually be, to test that paradigm.

I shudder to think of all the microservices code that sends a few bytes via their API in this way.