Jonas Smedegaard <notificati...@github.com> writes:
> the tool flowgrind seems like it might be an interesting backend for
> flent to support: https://github.com/flowgrind/flowgrind
>
> From its README:
>
>> Unlike most cross-platform testing tools, flowgrind can output some
>> transport layer information, which are usually internal to the TCP/IP
>> stack. For example, on Linux and FreeBSD this includes among others
>> the kernel's estimation of the end-to-end RTT, the size of the TCP
>> congestion window (CWND) and slow start threshold (SSTHRESH).
These values Flent can already extract (using the 'ss' tool). Just
enable --socket-stats :)
Also from its README:
> In contrast to similar tools like iperf or netperf it features a
> distributed architecture, where throughput and other metrics are
> measured between arbitrary flowgrind server processes.
...which makes me suspect it's not a very good fit for Flent.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/219#issuecomment-766769369
_______________________________________________
Flent-users mailing list -- flent-users@flent.org
To unsubscribe send an email to flent-users-le...@flent.org
