From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) (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 7D9723CB38 for ; Fri, 19 Jul 2019 17:02:56 -0400 (EDT) Received: by mail-ed1-f49.google.com with SMTP id r12so776140edo.5 for ; Fri, 19 Jul 2019 14:02:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=RU1Um11y2fLZhbc1qdbqOyS2RcoGVcHZ9fCdWbruIEQ=; b=D4CZ9HO34/pfXULPwWfKAEjveoISAV6gUgFCaAW7XQMPnFrVeMb61FhkQuJTcjaBhj 1XxDJFXYIjzt8bSVSWbAlqThg5TijLLe2faTasfcj6xMpE98yosN2wWxW94TJm5hm9pg jCzh63hqIQvApMVWqduhukxxkTiq2PxeO/Omnw6U3ADMLXiUYMuOgisbuHfAWMnKc5yM ewjrHpmjoFy32MnRK4ze9QlgAe3Ar4P/K1vdAPawye8E2L66rOYbfxlCG0K7vWFD7LxE NSCwMb9XypobNHUSJvJjGDypkG8jrwZjmMNFWAfcXRCmtZ3Kqhjo6KDXebZYMd8C4Aky La+w== X-Gm-Message-State: APjAAAVQaFMoOq9/8cg3B1IyAmD0/k3/V3IPjXNUbBnJPcMFs9/Lj/9s /fvq83BAW9fDH1JfWhyuAIujWQ== X-Google-Smtp-Source: APXvYqwkMXFtUqfqlbyk53FYgujzyecBY8g7qh8kK2HVfZ43InMIPy9sTTPrjZDWtLlbyCY9ameMzg== X-Received: by 2002:a50:b362:: with SMTP id r31mr49538382edd.14.1563570175658; Fri, 19 Jul 2019 14:02:55 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk (borgediget.toke.dk. [85.204.121.218]) by smtp.gmail.com with ESMTPSA id x12sm8621838edr.60.2019.07.19.14.02.54 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 19 Jul 2019 14:02:54 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 09AED1800B5; Fri, 19 Jul 2019 23:02:54 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Bob McMahon Cc: Make-Wifi-fast In-Reply-To: References: <874l3k70wi.fsf@toke.dk> X-Clacks-Overhead: GNU Terry Pratchett Date: Fri, 19 Jul 2019 23:02:53 +0200 Message-ID: <874l3h68le.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Make-wifi-fast] Fwd: iperf 2 "short term" road map X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2019 21:02:56 -0000 Bob McMahon writes: > Hi Toke, > > Do let me know. We're focused on the network i/o testing aspect (per being > a WiFi chip vendor) and are intentionally not trying to provide CPU load > metrics. (I think netperf provides both.) A feature we are adding is to > warn when we think something other than the socket reads() and writes() > have become bottlenecks, e.g. in a CPU constrained system it becomes an > "entangled metric" between i/o and CPU though still presents in network i/o > units which can be misleading to network device vendors. > > Also, many might want to consider monitoring "network power" which is > average throughput / latency or delay, i.e. "something good" / "something > bad" It's more socket-level statistics I'm after for Flent use; we generally run multiple instances (flows) concurrently and graph the results. This is the variables we currently extract from Netperf: output_vars = 'THROUGHPUT,LOCAL_CONG_CONTROL,REMOTE_CONG_CONTROL,' \ 'TRANSPORT_MSS,LOCAL_TRANSPORT_RETRANS,' \ 'REMOTE_TRANSPORT_RETRANS,LOCAL_SOCKET_TOS,' \ 'REMOTE_SOCKET_TOS,DIRECTION,ELAPSED_TIME,PROTOCOL,' \ 'LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,' \ 'REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,' \ 'LOCAL_BYTES_SENT,LOCAL_BYTES_RECVD,' \ 'REMOTE_BYTES_SENT,REMOTE_BYTES_RECVD' Some of these can be set as well (such as TOS and congestion control algorithm). Also, how safe is it to run an iperf server instance on the public internet? :) -Toke