Flent-users discussion archives
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] Re: [tohojo/flent] support for flowgrind (#219)
Date: Mon, 25 Jan 2021 04:04:00 -0800	[thread overview]
Message-ID: <tohojo/flent/issues/219/766769369@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/219@github.com>

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

Jonas Smedegaard <notifications@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

[-- Attachment #2: Type: text/html, Size: 2180 bytes --]

      reply	other threads:[~2021-01-25 12:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-23 18:14 [Flent-users] " Jonas Smedegaard
2021-01-25 12:04 ` Toke Høiland-Jørgensen [this message]

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=tohojo/flent/issues/219/766769369@github.com \
    --to=notifications@github.com \
    --cc=flent@noreply.github.com \
    --cc=reply+AHVNJP3C6OEGECKXDD4752F6DKKLBEVBNHHC6PTMXY@reply.github.com \
    --cc=subscribed@noreply.github.com \
    --subject='[Flent-users] Re: [tohojo/flent] support for flowgrind (#219)' \
    /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