From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 20 Feb 2016 15:01:49 +0100 From: tlaronde@polynum.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20160220140149.GA1093@polynum.com> References: <20160218113017.GB2756@polynum.com> <49010da5-9c4e-4399-8fbe-e4dae715063f@email.android.com> <20160219125246.GA345@polynum.com> <7cdd0c6898558feb7648d8d0bd356157@lilly.quanstro.net> <20160220103225.GA42@polynum.com> <901BC05C-A1C3-43F2-88F1-C96B28C00CD5@gmail.com> <20160220121147.GA515@polynum.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Re: [9fans] rtl8169 gbe slow Topicbox-Message-UUID: 863558e6-ead9-11e9-9d60-3106f5b1d025 On Sat, Feb 20, 2016 at 02:31:54PM +0100, hiro wrote: > what is the latency on WAN? When using traceroute, I have 42.6ms for a roundtrip (cf. with LAN: 0.23ms). But the very same machine, under NetBSD, with the very same ip address, downloads the very same file from the very same external server (downloads.kergis.com) in 17s, while hget(1) spends 6 minutes doing it. I wondered if the unsupported same chip integrated network card would be a problem. But disabling it via the BIOS doesn't change anything. Is there a way to trace what hget is doing/calling so that I can have a clue about the bottleneck? There is no transmission errors on the interface, so the problem is in the upper levels of TCP/IP. -- Thierry Laronde http://www.kergis.com/ http://www.arts-po.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C