From: Andrew Morton <andrewm@uow.edu.au>
To: Tim Sailer <sailer@bnl.gov>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Network Performance?
Date: Sat, 06 Jan 2001 22:11:40 +1100 [thread overview]
Message-ID: <3A56FD6C.93D09ABB@uow.edu.au> (raw)
In-Reply-To: <20010104013340.A20552@bnl.gov>, <20010104013340.A20552@bnl.gov>; from sailer@bnl.gov on Thu, Jan 04, 2001 at 01:33:40AM -0500 <20010105140021.A2016@bnl.gov>
Tim Sailer wrote:
>
> On Thu, Jan 04, 2001 at 01:33:40AM -0500, Tim Sailer wrote:
> > This may not be the right forum to ask this. If not, please let me know
> > where to ask.
> >
> > I have a Debian box with 2 NICs. Both 100/full duplex. This machine is
> > running as a ftp proxy (T.Rex suite). As part of the traffic going through the
> > box, some streams have 1000k window size for a certain reason. How do
> > I tune the NICs to handle the streams better? There are ways of doing this
> > on other OSs. Right now, the box only does about 1.8Mb when it should be doing
> > 80+Mb.
> >
> > Thanks,
> > Tim
> >
> > PS: This is really something to do with the window size and WAN latency.
> > The ultimate source and destination points are either Solaris or AIX
> > boxes. The files being sent are > 1GB in size.
> > The box does well when traffic goes in one NIC and out the other, as long
> > as the end point is local When it hits the WAN, it all dies. Traffic not
> > going through the box just flies right along, as long as both the end points
> > have the large tcp window size. Putting the Linux box in the middle is a
> > severe choke point. :(
>
> I have followed the suggestions in http://www.psc.edu/networking/perf_tune.html
> but I still can not get any kind of real throughput. 250kB is all I can
> get from the Linux box. Setting [r|w]mem_[default|max] larger than 16k
> makes no difference, smaller slows things down even more. Has anyone else
> ran across this and fixed it? I can't be the only one with a Linux box
> on a fat pipe looking for maximum throughput...
Tim,
this issue was discussed on the netdev mailing list a few weeks
back.
It's very unfortunate that the web archives of netdev
stopped working several months ago and there now appears
to be no web archive of netdev@oss.sgi.com.
Go to http://oss.sgi.com/projects/netdev/archive/ and
pull down the November and December archives.
The subject was "linux to solaris tcp issues on WAN".
The conclusion was "The problem is also fixed with
2.4.0-test12pre3". Dunno about kernel 2.2 though.
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-06 11:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 6:33 Network Performance? Tim Sailer
2001-01-05 19:00 ` Tim Sailer
2001-01-06 11:11 ` Andrew Morton [this message]
2001-01-06 15:48 ` Alan Cox
2001-01-08 4:51 ` Tim Sailer
2001-01-08 10:26 ` Andrew Morton
2001-01-08 14:06 ` Tim Sailer
2001-01-08 18:07 ` Erik Mouw
2001-01-09 13:55 ` Tim Sailer
2001-01-09 16:52 ` Martin Josefsson
2001-01-09 18:35 ` Tim Sailer
2001-01-08 18:40 ` Craig I. Hagan
2001-01-09 15:29 ` Tim Sailer
2001-01-08 19:58 ` John Heffner
2001-01-09 16:53 ` Tim Sailer
2001-01-09 19:29 ` John Heffner
2001-01-09 20:56 ` Tim Sailer
2001-01-11 10:00 ` Pekka Pietikainen
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=3A56FD6C.93D09ABB@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sailer@bnl.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.