public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Carrigan <dave@rudedog.org>
To: linux-kernel@vger.kernel.org
Subject: 2.4.16: Bizarre TCP throughput problems
Date: 08 Dec 2001 16:08:45 -0800	[thread overview]
Message-ID: <87d71pl0fm.fsf@cbgb.rudedog.org> (raw)

(I am not subscribed, so please CC me with any responses)

I am having a very problem with TCP throughput between two systems
running on my LAN. The problem system works fine with 2.4.14, but has
abysmal TCP throughput under 2.4.16, but only when talking to some
systems on the LAN. Here is a chart with some tests that I made:

 Client		Server	Protocol	Throughput
 cbgb-2.4.16	pern	NFS/UDP		~12 MB/s, .5s to copy a 5MB file
 cbgb-2.4.14	pern	HTTP/TCP	 12 MB/s, .5s to copy a 5MB file
 cbgb-2.4.16	pern	HTTP/TCP	7.45 KB/s, 300s to copy a 2MB file
 cbgb-2.4.16	pern	SCP/TCP		(Very poor; I was too impatient to measure)
 cbgb-2.4.16	heechee	SCP/TCP		  84 KB/s, 1 minute to copy a 5MB file
 cbgb-2.4.16	idoru	HTTP/TCP	  54 KB/s, 21s to copy a 1.2MB file
 heechee-2.4.16	pern	HTTP/TCP	1024 KB/s, 5s to copy a 5MB file
 vmware-2.2.19	pern	HTTP/TCP	 297 KB/s, 18s to copy a 5MB file
 pern		cbgb	SCP/TCP		 297 KB/s, 19s to copy a 5MB file

- cbgb is the problem system; with a tulip card.
- pern is the problem server; also with a tulip card.
- heechee is my firewall with a 8139too card.
- idoru is a server on the other end of a SSH VPN (DSL at both ends).
- vmware is a virtual vmware machine running inside of cbgb.

As you can see from the chart, NFS over UDP between cbgb and pern is
fine. However HTTP over TCP has terrible performance; 2.4.14 has orders
of magnitude better performance. It's not pern's problem, because
heechee has no trouble transferring the same file. It's also not
exclusively cbgb's fault, because it doesn't seem to have any problems
talking to idoru or to heechee. Nor are there any problems going the
other way (copying from cbgb to pern). The most bizarre thing is my test
on the vmware machine. It also doesn't seem to have problems
communicating with pern, even though it's a virtual machine that is
obviously using cbgb's hardware to do the copying. I should also add
that interactive ssh from cbgb to pern seems fine.

Pern's card is a 'Lite-On Communications Inc LNE100TX (rev 32)'.
Cbgb's card is a 'Lite-On Communications Inc LNE100TX [Linksys EtherFast 10/100] (rev 37)'.

Does anyone have any suggestions as to what's going on here?

-- 
Dave Carrigan (dave@rudedog.org)            | Yow! These PRESERVES should be
UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-DNS | FORCE-FED to PENTAGON
Seattle, WA, USA                            | OFFICIALS!!
http://www.rudedog.org/                     | 

             reply	other threads:[~2001-12-09  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09  0:08 Dave Carrigan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-09 10:20 2.4.16: Bizarre TCP throughput problems Manfred Spraul
2001-12-09 21:16 ` Dave Carrigan

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=87d71pl0fm.fsf@cbgb.rudedog.org \
    --to=dave@rudedog.org \
    --cc=linux-kernel@vger.kernel.org \
    /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