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



check the processor use on each end, and io stats for the disk.
try duplicating a similar copy using straight ftp (on a test/non-security 
needed file) and check your base network speed.
that might give you a quick hint.

-- 
Member/Associate of HLUG, HAL-PC, ACM, /., USENIX, ADSM.ORG, BCUMC, 
SBIB and other various random initials and anacronyms.


---------- Original Message -----------
From: heidi at midnighthax.com
To: discuss at blu.org
Sent: Mon, 9 Aug 2004 23:50:11 +0100
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
------- End of Original Message -------





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