From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vs23.mail.saunalahti.fi (vs23.mail.saunalahti.fi [193.64.193.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 78AFF3B29E for ; Tue, 31 Mar 2020 09:45:55 -0400 (EDT) Received: from vs23.mail.saunalahti.fi (localhost [127.0.0.1]) by vs23.mail.saunalahti.fi (Postfix) with ESMTP id 6021C205CE; Tue, 31 Mar 2020 16:45:54 +0300 (EEST) Received: from gw03.mail.saunalahti.fi (gw03.mail.saunalahti.fi [195.197.172.111]) by vs23.mail.saunalahti.fi (Postfix) with ESMTP id 545DD205B7; Tue, 31 Mar 2020 16:45:54 +0300 (EEST) Received: from ias.ebirdie (dsl-jnsbng12-54f83f-12.dhcp.inet.fi [84.248.63.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gw03.mail.saunalahti.fi (Postfix) with ESMTPSA id 3B9AB20003; Tue, 31 Mar 2020 16:45:52 +0300 (EEST) Received: from localhost ([::1]) by ias.ebirdie with esmtp (Exim 4.92) (envelope-from ) id 1jJHG5-0006q6-3s; Tue, 31 Mar 2020 16:48:49 +0300 From: Erkki Lintunen To: Tim Higgins , Make-Wifi-fast References: <1697eb13-068d-f518-35d6-1d1495feab40@smallnetbuilder.com> Message-ID: <6160f18c-948c-65f2-41d1-82c35136835d@iki.fi> Date: Tue, 31 Mar 2020 16:48:49 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <1697eb13-068d-f518-35d6-1d1495feab40@smallnetbuilder.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 31 Mar 2020 10:16:37 -0400 Subject: Re: [Make-wifi-fast] Flent traffic direction convention 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: Tue, 31 Mar 2020 13:45:55 -0000 On 3/26/20 11:22 PM, Tim Higgins wrote: > Second question: Is there any documentation that can help me figure out > exactly what traffic is running in each test type? Not exactly an answer to the question. I found following pages very helpful when three years ago I challenged myself with Flent to measure WiFi network performance and max it out with network devices I had at hand at the time. (One ap blew up it's two capasitors. Visually and operationally the ap was working as normal but measurements showed drastic drop in performance. Light odor and inspection of el-capasitor burned tops did confirm the hard to believe experience.) The above page provides link to this page. Experience showed up Flent's feature to compare data sets very educating and powerfull, not only with the box-plot chart as the pages show. Took time to get mentaly bend to read and interpret the Flent charts instead of only numbers I was used to with iperf and other tools. In my quest I did a change, measured it, compared to the previous set and reviewed, if the change showed any measurable effect. Finally I compared the sets of the very first and the last. I was totally driven by measurements on my way myth busting many my beliefs for a performant network. The quest changed my definition for "getting max out of a network". Now the max is all quantities in effect at any time: fairness, lowest possible latency and highest possible bitrate. Looking at many published benchmarks today, I still think, max seams to mean just a maximum bitrate and other qualities are _supposed_ to derive from it. Hope this is for any help. - Erkki