Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

diagnosing network speed bottlenecks



On Wed, Sep 30, 2009 at 06:49:42AM -0400, Daniel Feenberg wrote:
> On Wed, 30 Sep 2009, Greg Rundlett (freephile) wrote:
> 
> > I'm not a network packet-sniffing blood-hound, so I need some help of
> > the mere-mortal variety :-)
> 
> Latency is a problem that springs to mind. Have you tried any of the 
> suggestions here?
> 
>     http://www.psc.edu/networking/projects/tcptune/

>From that page:

"NB: Recent versions of Linux (version 2.6.17 and later) have full
autotuning with 4 MB maximum buffer sizes. Except in some rare cases,
manual tuning is unlikely to substantially improve the performance of these
kernels over most network paths, and is not generally recommended"

And:

"Note that both ends of a TCP connection must be properly tuned
independently, before it will support high speed transfers."

So it's not really applicable to Greg's case.

-ben

--
a good horse runs even at the shadow of a whip.               <buddha>






BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org