9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] USB3 1Gb ethernet card working on 9legacy (rpi 4)
Date: Thu, 4 Aug 2022 11:13:00 +0100	[thread overview]
Message-ID: <69fcc16897189de2ecdae733cf743eef@hamnavoe.com> (raw)
In-Reply-To: <d8aed821-a1be-d225-3675-f2f49af6aff6@SDF.ORG>

> I don't know any reliable server with good bandwidth serving without tls

I am able to connect to your example arch.mirror.constant.com using
both http and https.

Something is going on with usb ethernet and tls which I don't understand.
Could it be as simple as different block sizes interacting with the usb
packet size?

I modified hget -v option to print the number of reads in each second, as
well as the original bytes-so-far and bytes-total. My internet wire speed
is about 40 megabit/sec.

Using the pi4 built-in ethernet, I see this:

term% url=//arch.mirror.constant.com/images/v20220801.71902/Arch-Linux-x86_64-basic-20220801.71902.qcow2term% 5.hget -v -o /dev/null http:$url
1 1074 513671168
154 236298 513671168
1891 4664898 513671168
1885 9351954 513671168
1952 14040462 513671168
1948 18715902 513671168
1908 23411670 513671168
2035 28095822 513671168
1992 32781426 513671168
1995 37459770 513671168
1945 42146826 513671168
...
term% 5.hget -v -o /dev/null https:$url
1 1670 513671168
136 1113734 513671168
571 5791366 513671168
569 10452614 513671168
571 15130246 513671168
568 19783302 513671168
570 24452742 513671168
569 29113990 513671168
573 33808006 513671168
568 38461062 513671168
542 42901126 513671168
...

Using a 100Mb/s usb2 ether adapter on the same pi4, I see this:

term% 5.hget -v -o /dev/null http:$url
1 1074 513671168
662 1261410 513671168
2129 5896194 513671168
2121 10525170 513671168
2259 15167214 513671168
2212 19804902 513671168
2223 24442590 513671168
2195 29112222 513671168
2175 33800730 513671168
2197 38479074 513671168
2244 43164678 513671168
...
term% 5.hget -v -o /dev/null https:$url
1 1670 513671168
75 614022 513671168
132 1695366 513671168
2 1711750 513671168
4 1744518 513671168
128 2793094 513671168
10 2875014 513671168
24 3071622 513671168
98 3874438 513671168
4 3907206 513671168
130 4972166 513671168
...

Needs deeper investigation.


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T668643d11149fab4-Mbdc3913dcd77a8be18193e66
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-08-04 10:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 17:58 adr
2022-07-31 18:08 ` hiro
2022-07-31 18:09   ` adr
2022-07-31 21:35 ` Richard Miller
2022-08-01  9:16 ` Richard Miller
2022-08-01 16:29   ` adr
2022-08-02  8:50     ` Richard Miller
2022-08-03  0:34       ` adr
2022-08-03  3:00         ` adr
2022-08-03 10:57           ` Richard Miller
2022-08-03 18:46             ` adr
2022-08-04 10:13               ` Richard Miller [this message]
2022-08-04 11:56                 ` ori
2022-08-04 19:34                 ` adr
2022-08-05 12:14                   ` ori
2022-08-01 16:43   ` adr
2022-08-01 17:06     ` adr
2022-08-02  3:45       ` Lucio De Re
2022-08-02  9:07     ` Richard Miller
2022-08-03  0:52       ` adr
2022-08-03  1:08         ` adr
2022-08-03 12:41           ` Richard Miller
2022-08-03 18:47             ` adr

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=69fcc16897189de2ecdae733cf743eef@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).