From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] USB3 1Gb ethernet card working on 9legacy (rpi 4)
Date: Thu, 04 Aug 2022 07:56:02 -0400 [thread overview]
Message-ID: <E6BFCEEB1AEF64CC9A92D56AC5138E1B@eigenstate.org> (raw)
In-Reply-To: <69fcc16897189de2ecdae733cf743eef@hamnavoe.com>
Quoth Richard Miller <9fans@hamnavoe.com>:
> I am able to connect to your example arch.mirror.constant.com using
> both http and https.
Same.
> 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.
I'm not certain that it's only USB ethernet.
On my (gigabit) ethernet, my CPU server is about 15% the speed of
my Linux work machine, averaging something like 15 MiB/second.
But with different URLs (I picked some OpenBSD mirrors), the results
vary wildly:
cpu% hget http:$url | tput
10.98 MB/s
20.70 MB/s
17.07 MB/s
15.59 MB/s
<snip>
10.70 MB/s
10.77 MB/s
<snip>
15.17 MB/s
15.26 MB/s
$ curl -o /dev/null http:$url <
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 489M 100 489M 0 0 105M 0 0:00:04 0:00:04 --:--:-- 105M
Compare this one, where 9front beats Linux handily:
cpu% url=//ftp4.usa.openbsd.org/pub/OpenBSD/7.1/amd64/install71.img
cpu% hget http:$url | tput
60.20 MB/s
71.13 MB/s
70.77 MB/s
71.21 MB/s
69.97 MB/s
70.15 MB/s
72.19 MB/s
73.59 MB/s
$ curl -o /dev/null http:$url
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 664M 100 664M 0 0 24.7M 0 0:00:26 0:00:26 --:--:-- 25.1M
And:
% hget http:$url | tput
1.26 MB/s
1.54 MB/s
1.54 MB/s
1.45 MB/s
<snip>
3.53 MB/s
$ curl -o /dev/null http:$url
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
27 664M 27 183M 0 0 22.7M 0 0:00:29 0:00:08 0:00:21 23.4M
and:
% hget http:$url | tput
33.00 MB/s
37.52 MB/s
36.93 MB/s
<snip>
38.97 MB/s
39.09 MB/s
$ curl -o /dev/null http:$url
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 664M 100 664M 0 0 90.0M 0 0:00:07 0:00:07 --:--:-- 93.7M
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T668643d11149fab4-M6384a056753c4f907745c22c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-08-04 11:56 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
2022-08-04 11:56 ` ori [this message]
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=E6BFCEEB1AEF64CC9A92D56AC5138E1B@eigenstate.org \
--to=ori@eigenstate.org \
--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).