From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bobcat.rjmcmahon.com (bobcat.rjmcmahon.com [45.33.58.123]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 2300D3B2A4; Mon, 9 Jan 2023 14:20:00 -0500 (EST) Received: from mail.rjmcmahon.com (bobcat.rjmcmahon.com [45.33.58.123]) by bobcat.rjmcmahon.com (Postfix) with ESMTPA id 656D21B252; Mon, 9 Jan 2023 11:19:59 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 bobcat.rjmcmahon.com 656D21B252 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rjmcmahon.com; s=bobcat; t=1673291999; bh=S+4Z1H1SsJ7/fcp4azwPwcds1OIuandY8qi/5WZNq2I=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=U9aNVQfP8shnECtYJGrudV/KI4X0UT1U4fN8fqTlsFqVaTu95xlBI2ZBUsHM+HlhF tnDletVm+atohS8tan3cxCRMd0+noVyNGxtXDDJzwXadRQttgrQWS491xZJiXMCxoq VeDryXMaaHv7Fcun5noEwJwsFnO02kVw8V0Wqcgw= MIME-Version: 1.0 Date: Mon, 09 Jan 2023 11:19:59 -0800 From: rjmcmahon To: "Livingood, Jason" Cc: Dave Taht , starlink@lists.bufferbloat.net, Rpm , libreqos , bloat In-Reply-To: <77CCAD19-07E0-4F9E-88C1-D207CF7BF376@cable.comcast.com> References: <1672786712.106922180@apps.rackspace.com> <77CCAD19-07E0-4F9E-88C1-D207CF7BF376@cable.comcast.com> Message-ID: <83ffc0dad19e3343e49271889369cefc@rjmcmahon.com> X-Sender: rjmcmahon@rjmcmahon.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Rpm] [EXTERNAL] Re: [Starlink] Researchers Seeking Probe Volunteers in USA X-BeenThere: rpm@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: revolutions per minute - a new metric for measuring responsiveness List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2023 19:20:00 -0000 User based, long duration tests seem fundamentally flawed. QoE for users is driven by user expectations. And if a user won't wait on a long test they for sure aren't going to wait minutes for a web page download. If it's a long duration use case, e.g. a file download, then latency isn't typically driving QoE. Not: Even for internal tests, we try to keep our automated tests down to 2 seconds. There are reasons to test for minutes (things like phy cals in our chips) but it's more of the exception than the rule. Bob >> 0) None of the tests last long enough. > > The user-initiated ones tend to be shorter - likely because the > average user does not want to wait several minutes for a test to > complete. But IMO this is where a test platform like SamKnows, Ookla's > embedded client, NetMicroscope, and others can come in - since they > run in the background on some randomized schedule w/o user > intervention. Thus, the user's time-sensitivity is no longer a factor > and a longer duration test can be performed. > >> 1) Not testing up + down + ping at the same time > > You should consider publishing a LUL BCP I-D in the IRTF/IETF - like in > IPPM... > > JL > > _______________________________________________ > Rpm mailing list > Rpm@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/rpm