I use cable modem, with download speed tests often surpassing 3mb. Real world file downloads usually stay in the 450k/sec range. Tonight a friend of mine needed a large file I've got here, so I set up IIS on an XP Pro pc and let him FTP in and get the file. He also uses cable modem from the same provider. We were blown away by the slow speed of this file transfer. It never got above 40k/sec, and it spent a lot of the time around 30k/sec. Now, I fully realize that cable is asynchronous, and I know upload speeds on a basic residential account will be modest, but doesn't 30k seem very slow? My question is: what factors influence the speed in a case like this? The computer I was using here is a decent machine - 1.8ghz P4, 512mb RAM,
7200rpm hard drive - and it's wired to a netgear router. Speeds on my network are certainly acceptable. Does FTP itself have something to do with it? The utility we used (FTP Voyager)?
After writing that question I ran several speed tests, and the average result was:
3234 down
176 up
If, indeed, my real-world download speed is 450k/sec - then my real-world speed is approximately 15% of the speed-test speed. If that ratio is applied to the upload speed, then my real-world upload speed should be around 27k/sec - right at the speeds we were getting earlier. Hmm . . . maybe I just answered my own question 8 /)
However, I've always thought my limited download speed (the "real-world" download speed) was a result of the host server's limited upload speed, rather than any limitation on my down speed. (??)
jake