public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Sailer <sailer@bnl.gov>
To: "Craig I. Hagan" <hagan@cih.com>
Cc: Andrew Morton <andrewm@uow.edu.au>,
	linux-kernel@vger.kernel.org, jfung@bnl.gov
Subject: Re: Network Performance?
Date: Tue, 9 Jan 2001 10:29:38 -0500	[thread overview]
Message-ID: <20010109102938.B28548@bnl.gov> (raw)
In-Reply-To: <20010108090644.A12440@bnl.gov> <Pine.LNX.4.20.0101081324430.30022-100000@www.cih.com>
In-Reply-To: <Pine.LNX.4.20.0101081324430.30022-100000@www.cih.com>; from hagan@cih.com on Mon, Jan 08, 2001 at 01:40:57PM -0500

On Mon, Jan 08, 2001 at 01:40:57PM -0500, Craig I. Hagan wrote:
> > 101 packets transmitted, 101 packets received, 0% packet loss
> > round-trip min/avg/max = 109.6/110.3/112.2 ms
> > 
> > > Does the problem occur in both directions?
> > 
> > Good question. I'll find out.
> > 
> > > Are you _sure_ the window size is being set correctly? How
> > > is it being set?
> > 
> > I'm fairly sure. We echo the value to the file. catting it back
> > shows the correct value. If we go lower than default, it slows
> > down even more.
> 
> what are you setting it to on the solaris machine? what window
> sizes have you tried?
> 
> Your pipe looks like it will have quite a few bits in flight due to its

Yup. That's why the tuning. WAN performance here is very important.

> latency. From my quick guess math, which sucks, it appears that you can fit 1.2
> to 1.5 megabytes on the wire (100mbit machine<-> machine) times 100-120ms wire

Hmm. 100/8 is about 12, no? 

> time. This is a rather large number, so you may want to see what hosts really
> support, perhaps starting with 64k or 128k and work up. Make sure that you have
> window scaling turned on if you go with very large windows.

Yes, we have that enabled too.

> Also, have you upped your socket buffers to match your window sizes?

We are using straight ftp for the testing.

> Last, solaris tends to have poorly tuned tcp values out of the box, look at
> this link and tune the solaris stack to better reflect reality.
> http://www.google.com/search?q=cache:www.rvs.uni-hannover.de/people/voeckler/tune/EN/tune.html+%2Bwan+%2Bwindow+%2Bscale+%2Bsize+%2Bnetwork&hl=en
> 
> linux tuning has a decent amount of data in the docs section of the kernel
> sources.

I'll take a look. THanks.

Tim

-- 
Tim Sailer <sailer@bnl.gov> Cyber Security Operations
Brookhaven National Laboratory  (631) 344-3001
-
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/

  reply	other threads:[~2001-01-09 15:30 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
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 [this message]
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=20010109102938.B28548@bnl.gov \
    --to=sailer@bnl.gov \
    --cc=andrewm@uow.edu.au \
    --cc=hagan@cih.com \
    --cc=jfung@bnl.gov \
    --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