From: Will Hawkins <hawkinsw@obs.cr>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Dave Täht" <dave.taht@gmail.com>, Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] latest goresponsiveness test over starlink
Date: Sun, 24 Jul 2022 02:31:18 -0400 [thread overview]
Message-ID: <CADx9qWg-E+F=vmsRRA-B0dVgyD9bv+QrUr=9L=9QSGx9dLu+_g@mail.gmail.com> (raw)
In-Reply-To: <6C83DEDA-B3A0-42A2-BAE9-F224968B4802@gmx.de>
Great suggestions. I will continue to play with the UI. It looks like
these conditions for timeout might be changing in future iterations of
the spec, so I will keep my eye on how it progresses. Thanks again for
the suggestions!
Will
PS: How do you like Starlink overall?
On Sat, Jul 23, 2022 at 11:38 PM Sebastian Moeller <moeller0@gmx.de> wrote:
>
> Hi Will,
>
> Regarding my 'fat pipe' link, given that the current draft seems to recommend the 20 seconds, how about simply starting with that value, but on failure to achieve saturation do one of the following:
> a) give a more detailed error message instructing the user to use the sattimeout option, maybe by printing the used command with '-sattimeout 60' or so added, so that simple copy and paste might allow the user to try again.
> b) do not stop the code on this failure, but ask the user interactively whether to try again with a larger sattimeout value.
>
> Whether that will help in the starlink case I can only guess...
>
> Regards
> Sebastian
>
> On 23 July 2022 23:19:28 CEST, Will Hawkins <hawkinsw@obs.cr> wrote:
>>
>> I am sorry that I am late to this thread. I would love to work
>> together to see if there are some things that we could do to make the
>> client more robust when someone uses it from "constrained" (to put it
>> nicely) environments!
>>
>> Will
>>
>> On Fri, Jul 22, 2022 at 4:26 PM Sebastian Moeller via Rpm
>> <rpm@lists.bufferbloat.net> wrote:
>>>
>>>
>>> Hi Dave,
>>>
>>> maybe try:
>>>
>>> time ./networkQuality --config mensura.cdn-apple.com --port 443 --path /api/v1/gm/config -extended-stats -sattimeout 60
>>>
>>> to extend the maximal time to achieve saturation to a minute. I notice than of a fat path (1000/1000 Mbps) 20 seconds are not enough to achieve saturation, and maybe things take while on starlink as well?
>>>
>>> Regards
>>> Sebastian
>>>
>>>
>>>
>>>
>>>> On Jul 22, 2022, at 21:00, Dave Taht via Rpm <rpm@lists.bufferbloat.net> wrote:
>>>>
>>>> First attempt timed out. Second attempt...
>>>>
>>>> ./networkQuality --config mensura.cdn-apple.com --port 443 --path
>>>> /api/v1/gm/config
>>>> 07-22-2022 18:58:53 UTC Go Responsiveness to mensura.cdn-apple.com:443...
>>>> Download: 34.351 Mbps ( 4.294 MBps), using 20 parallel connections.
>>>> Upload: 3.653 Mbps ( 0.457 MBps), using 20 parallel connections.
>>>> RPM: 438
>>>>
>>>>
>>>>
>>>> --
>>>> FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
>>>> Dave Täht CEO, TekLibre, LLC
>>>> ________________________________
>>>> Rpm mailing list
>>>> Rpm@lists.bufferbloat.net
>>>> https://lists.bufferbloat.net/listinfo/rpm
>>>
>>> ________________________________
>>> Rpm mailing list
>>> Rpm@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/rpm
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2022-07-24 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 19:00 Dave Taht
2022-07-22 20:26 ` Sebastian Moeller
2022-07-23 21:19 ` Will Hawkins
2022-07-24 3:38 ` Sebastian Moeller
2022-07-24 6:31 ` Will Hawkins [this message]
2022-07-24 10:05 ` Sebastian Moeller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADx9qWg-E+F=vmsRRA-B0dVgyD9bv+QrUr=9L=9QSGx9dLu+_g@mail.gmail.com' \
--to=hawkinsw@obs.cr \
--cc=dave.taht@gmail.com \
--cc=moeller0@gmx.de \
--cc=rpm@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox