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 a slow network



First, are you sure you don't have the network running at 10M, and not 100.

Second, scp IS SLOW!  I don't know how fast your machines are, but this
could be the problem.  Send one msg in the clear (use FTP.)  Is it much
faster?  If not, you've eliminated encryption/decryption problems as the
culprit.

If I had to guess, with slow hardware, I would say that your scp task's are
slowing things down.  What do others have to say?


--jg



----- Original Message ----- 
From: <heidi at midnighthax.com>
To: <discuss at blu.org>
Sent: Monday, August 09, 2004 6:50 PM
Subject: Diagnosing a slow network


> I'm trying to work out why copying a file across my network is so slow.
> There are four Linux boxes connected to a 100Mb switch, and copying a
300Mb
> from one system to another runs at 500K/second. The systems aren't busy,
so
> it could be a network card problem, a hard disk being slow, or - what? I'm
> using scp to do the copy, so there will be some overhead with encryption,
> but 500K/sec is way too slow. Any ideas on how to troubleshoot this?
>
> H
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss
>





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