From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F12393B29E for ; Sun, 14 Jun 2020 10:37:09 -0400 (EDT) Received: by mail-qk1-x72e.google.com with SMTP id q8so13351629qkm.12 for ; Sun, 14 Jun 2020 07:37:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=EOCIr8hJsCR+OgzROfaSZCxgv2Evo6bOnGjJsPqozgY=; b=HCMYAP8lvhVz+j7mJP7dk9uFavWBWPidT+T2lop3CE0pBOy2RB/b6IMV/NxvX/REo5 lfM62NyQP8Ch6CkxK5gbTvynW2HsBHDg54p1qPeaak+whwCf/erRV2k4twXqGrU3qDMw hGkFvAWD4atF28tgLnRikxjNkY8RfIANSJ0Gu3XroyJBSUq4pV+UJHbn5US7wGEJl20l aVpHUqAOWCBKB4na84ZhBLtHk/ct2YmkRPZeNoC6JSEl4zLuT7bFjxo1BVhmyH7KrthZ fptgooJNZN7iZdz5wZ9NVHRSbpfFjQ/mbOen3ApCAsMVXv2mxlrBzQuqCk1PNUZ13/m5 GKaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=EOCIr8hJsCR+OgzROfaSZCxgv2Evo6bOnGjJsPqozgY=; b=l91a6a5JoLC2b4FqlTlTZQk/+OIwerSdIlbYWEeXHENntX1S6FGkBGVdL8/z0KnSZd 7s+/MlMEPIA9YCTI1mvATOj/Fs9fw0S1kLeOx5pKWnK5rELiEgk1T0uDorjPZOfk+x6D mz5cGlKh5RSdctfXwCV4quCOk6v8iZ/Rs6nmaoHNHwYHRNcw+SRGHF3CTkSFHlIZYxYE 3o1V+A0r+0qjwK/p7Tigxq8fayhHVo0RIVQLbHQ70TEIwJ1gKTM55hZVPwEZCX6cWVeb IFKB49lirfKXCZCdJgPlNFRsDYzFSlXbeCoq6EVrUiZ7AJUY8AfTFXOHUIndGLOgVkqQ u0Ig== X-Gm-Message-State: AOAM5306Cox1/BqtuCv4SSA7P5mU+ufebc0v9hrUELyN8lkCTvbXiRtX WhitVflBUk6669ObFKz0skxz2tCsnapMotH9ysT5oe9AZpQ= X-Google-Smtp-Source: ABdhPJx6T5oPw4vRM4Cfgd7tIeLJM3HjA3y/ATyrxsoo/fWN5yabbw1paiwWhO9lHzPHxy4gYS6QZ1fCiS5uBQ9oazI= X-Received: by 2002:a37:5f87:: with SMTP id t129mr11120975qkb.121.1592145429257; Sun, 14 Jun 2020 07:37:09 -0700 (PDT) MIME-Version: 1.0 From: Sergio Belkin Date: Sun, 14 Jun 2020 11:36:56 -0300 Message-ID: To: bloat@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="000000000000bde70a05a80c3eed" Subject: [Bloat] Is still netperf a valid tool? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jun 2020 14:37:10 -0000 --000000000000bde70a05a80c3eed Content-Type: text/plain; charset="UTF-8" Hi, I've seen that many of the recommended tools to diagnose/troubleshoot bufferbloat use netperf. Netperf in https://github.com/HewlettPackard/netperf has many years of inactivity. In fact, in recent versions of distros don't include it. So, my question is: is still netperf a reliable tool? Thanks in advance! -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org --000000000000bde70a05a80c3eed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
I've seen that many of the recommen= ded tools to diagnose/troubleshoot bufferbloat use netperf.
Netpe= rf in https://github.= com/HewlettPackard/netperf has many years of inactivity. In fact, in re= cent versions of distros don't include it.
So, my question is= : is still netperf a reliable tool?
Thanks in advance!
--
--
Sergio Belki= n
LPIC-2 Certified - ht= tp://www.lpi.org
--000000000000bde70a05a80c3eed--