From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 38F783CB37 for ; Tue, 6 Jul 2021 10:46:23 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id ED7A438A43; Tue, 6 Jul 2021 10:48:49 -0400 (EDT) Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id N_0-RRZIALBL; Tue, 6 Jul 2021 10:48:47 -0400 (EDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 71F7638A42; Tue, 6 Jul 2021 10:48:47 -0400 (EDT) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 3A61065E; Tue, 6 Jul 2021 10:46:19 -0400 (EDT) From: Michael Richardson To: Jonathan Morton cc: Matt Mathis , bloat In-Reply-To: <5C8DA517-01DE-477F-9B3D-952D953EEC89@gmail.com> References: <5C8DA517-01DE-477F-9B3D-952D953EEC89@gmail.com> X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Date: Tue, 06 Jul 2021 10:46:19 -0400 Message-ID: <25880.1625582779@localhost> Subject: Re: [Bloat] Credit and/or collaboration on a responsiveness metric? 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: Tue, 06 Jul 2021 14:46:23 -0000 Jonathan Morton wrote: > My idea was simply to express delays and latencies as a frequency, in > Hz, so that "bigger numbers are better", rather than always in > milliseconds, where "smaller numbers are better". The advantage of Hz > is that you can directly compare it to framerates of video or > gameplay. Marketing people will get this better. They already know that higher-Mhz is better :-)