tech-kern archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: /dev/random is hot garbage
On Mon, Jul 22, 2019 at 10:08 AM Havard Eidnes <he%netbsd.org@localhost> wrote:
>
> >> >> ftp://golden-delicious.urc.uninett.no/pub/rust/rust-std-1.35.0-i686-unknown-netbsd.tar.gz
> >> >
> >> > Why is it not on ftp.NetBSD.org, with other bootstrap kits?
> >>
> >> Because copying the bootstrap kits takes forever...
> >> I'm in the process of copying them over, but it's a multi-day
> >> effort.
> >
> > Because scp is blocked waiting for random bits? :)
>
> Heh.
>
> I think there's just some bad network in the middle here. No
> packet loss, though, but the congestion window nearly never opens
> up above 64KB. Then there's the application-window in ssh
> itself, but we have the HPN additions on both client and server,
> so it *should* be able to scale that higher than 64KB(?)
>
>
> : {5} ; iperf3 -i 3 -t 30 -c ftp.netbsd.org
> Connecting to host ftp.netbsd.org, port 5201
> [ 6] local 2001:700:1:0:eeb1:d7ff:fe59:fbaa port 57151 connected to 2001:470:a085:999::21 port 5201
> [ ID] Interval Transfer Bandwidth Retr Cwnd
> [ 6] 0.00-3.01 sec 1.03 MBytes 2.87 Mbits/sec 0 5.50 KBytes
> [ 6] 3.01-6.01 sec 678 KBytes 1.85 Mbits/sec 0 6.88 KBytes
> [ 6] 6.01-9.00 sec 928 KBytes 2.54 Mbits/sec 0 13.8 KBytes
> [ 6] 9.00-12.02 sec 1.23 MBytes 3.43 Mbits/sec 0 37.1 KBytes
> [ 6] 12.02-15.01 sec 1.15 MBytes 3.22 Mbits/sec 0 22.0 KBytes
> [ 6] 15.01-18.01 sec 1.16 MBytes 3.25 Mbits/sec 0 113 KBytes
> [ 6] 18.01-21.01 sec 1.97 MBytes 5.53 Mbits/sec 0 75.6 KBytes
> [ 6] 21.01-24.01 sec 796 KBytes 2.17 Mbits/sec 0 27.5 KBytes
> [ 6] 24.01-27.01 sec 1.36 MBytes 3.80 Mbits/sec 0 39.9 KBytes
> [ 6] 27.01-30.01 sec 1.12 MBytes 3.12 Mbits/sec 0 68.8 KBytes
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval Transfer Bandwidth Retr
> [ 6] 0.00-30.01 sec 11.4 MBytes 3.18 Mbits/sec 0 sender
> [ 6] 0.00-30.01 sec 10.9 MBytes 3.05 Mbits/sec receiver
>
> iperf Done.
> : {6} ; iperf3 -4 -i 3 -t 30 -c ftp.netbsd.org
> Connecting to host ftp.netbsd.org, port 5201
> [ 6] local 158.38.62.77 port 59576 connected to 199.233.217.201 port 5201
> [ ID] Interval Transfer Bandwidth Retr Cwnd
> [ 6] 0.00-3.00 sec 261 KBytes 713 Kbits/sec 0 11.3 KBytes
> [ 6] 3.00-6.01 sec 215 KBytes 586 Kbits/sec 0 1.41 KBytes
> [ 6] 6.01-9.00 sec 217 KBytes 593 Kbits/sec 0 11.3 KBytes
> [ 6] 9.00-12.00 sec 178 KBytes 486 Kbits/sec 0 28.3 KBytes
> [ 6] 12.00-15.01 sec 263 KBytes 718 Kbits/sec 0 2.83 KBytes
> [ 6] 15.01-18.01 sec 212 KBytes 580 Kbits/sec 0 21.2 KBytes
> [ 6] 18.01-21.00 sec 270 KBytes 738 Kbits/sec 0 7.07 KBytes
> [ 6] 21.00-24.02 sec 322 KBytes 877 Kbits/sec 0 32.5 KBytes
> [ 6] 24.02-27.01 sec 266 KBytes 727 Kbits/sec 0 9.90 KBytes
> [ 6] 27.01-30.02 sec 170 KBytes 462 Kbits/sec 0 5.66 KBytes
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval Transfer Bandwidth Retr
> [ 6] 0.00-30.02 sec 2.32 MBytes 648 Kbits/sec 0 sender
> [ 6] 0.00-30.02 sec 2.21 MBytes 617 Kbits/sec receiver
>
> iperf Done.
> : {7} ; traceroute -I ftp.netbsd.org
> traceroute to ftp.netbsd.org (199.233.217.201), 64 hops max, 40 byte packets
> 1 uninett-gsw1 (158.38.62.8) 0.986 ms 0.775 ms 2.415 ms
> 2 teknobyen-gw4 (128.39.70.8) 0.788 ms 0.790 ms 0.781 ms
> 3 trd-gw (128.39.230.116) 0.762 ms 29.401 ms 6.203 ms
> 4 oslo-gw1 (128.39.255.24) 8.750 ms 8.730 ms 8.764 ms
> 5 se-tug.nordu.net (109.105.102.108) 15.597 ms 15.703 ms 15.563 ms
> 6 se-fre.nordu.net (109.105.97.1) 15.474 ms 21.950 ms 15.410 ms
> 7 s-b3-link.telia.net (213.248.97.17) 15.915 ms 17.054 ms 15.955 ms
> 8 s-bb4-link.telia.net (62.115.119.110) 15.915 ms 15.893 ms 15.799 ms
> 9 ffm-bb2-link.telia.net (62.115.138.105) 39.084 ms 39.145 ms 39.210 ms
> 10 ffm-b1-link.telia.net (62.115.137.167) 37.740 ms 37.362 ms 41.580 ms
> 11 f5networks-ic-341210-ffm-b1.c.telia.net (62.115.169.109) 38.844 ms 38.898 ms 38.871 ms
> 12 pccw-bb-fra1.sjc1.defense.net (107.162.2.50) 176.183 ms 174.953 ms 189.680 ms
> 13 107.162.79.2 (107.162.79.2) 173.713 ms 181.094 ms 180.158 ms
> 14 107.162.16.70 (107.162.16.70) 181.437 ms 191.085 ms 185.156 ms
> 15 morden.netbsd.org (199.233.217.201) 179.934 ms 194.359 ms 194.508 ms
> : {8} ;
> : {8} ; traceroute6 -I ftp.netbsd.org
> traceroute6 to ftp.netbsd.org (2001:470:a085:999::21) from 2001:700:1:0:eeb1:d7ff:fe59:fbaa, 64 hops max, 16 byte packets
> 1 uninett-gsw2 0.818 ms 0.793 ms 0.782 ms
> 2 uninett-gsw1 0.793 ms 0.793 ms 0.761 ms
> 3 teknobyen-gw4 0.79 ms 0.794 ms 0.789 ms
> 4 trd-gw 0.784 ms 0.789 ms 0.778 ms
> 5 oslo-gw1 8.774 ms 9.899 ms 8.611 ms
> 6 se-tug.nordu.net 15.581 ms 23.129 ms 18.114 ms
> 7 se-fre.nordu.net 15.516 ms 15.499 ms 15.492 ms
> 8 dk-ore.nordu.net 20.232 ms 20.262 ms 21.075 ms
> 9 kbn-b4-link.telia.net 20.961 ms 20.199 ms 20.28 ms
> 10 kbn-bb3-v6.telia.net 40.82 ms 41.092 ms 42.064 ms
> 11 hbg-bb1-v6.telia.net 39.188 ms 39.122 ms 39.089 ms
> 12 ffm-bb3-v6.telia.net 39.414 ms 39.282 ms 39.279 ms
> 13 ffm-b2-v6.telia.net 39.097 ms 38.318 ms 39.017 ms
> 14 ve309.core1.fra1.he.net 39.002 ms 39.005 ms 39.145 ms
> 15 * 100ge6-1.core1.ams1.he.net 35.309 ms 43.221 ms
> 16 * * *
> 17 100ge8-1.core1.dub1.he.net 47.971 ms * 69.337 ms
> 18 100ge5-2.core1.nyc5.he.net 116.144 ms 116.063 ms 116.194 ms
> 19 100ge4-2.core1.nyc4.he.net 116.127 ms 116.314 ms 116.285 ms
> 20 100ge8-1.core1.sjc2.he.net 174.799 ms 174.588 ms 174.698 ms
> 21 10ge4-4.core1.sjc1.he.net 174.596 ms 184.156 ms 174.746 ms
> 22 e0-50.core4.fmt1.he.net 186.664 ms 186.079 ms 186.323 ms
> 23 tserv1.fmt1.he.net 175.402 ms 175.033 ms 175.117 ms
> 24 tunnel426-pt.tunnel.tserv1.fmt.ipv6.he.net 175.876 ms 175.837 ms 175.348 ms
> 25 ftp.NetBSD.org 175.489 ms 175.659 ms 175.696 ms
> : {9} ;
>
> Meanwhile, my rsync's are going:
>
> rust-std-1.31.1-armv7-unknown-netbsd-eabihf.tar.gz
> 71,603,203 100% 34.01kB/s 0:34:15 (xfr#12, to-chk=28/69)
> rust-std-1.31.1-i686-unknown-netbsd.tar.gz
> 71,783,116 100% 33.88kB/s 0:34:27 (xfr#13, to-chk=27/69)
> rust-std-1.31.1-powerpc-unknown-netbsd.tar.gz
> 70,015,527 100% 14.10kB/s 1:20:50 (xfr#14, to-chk=26/69)
>
> Regards,
>
> - Håvard
Is that defense.net your own outgoing protection or is there a route
messed up? I've used them for inline stuff before.
My traceroute is different to say the least!
Home |
Main Index |
Thread Index |
Old Index