On Fri, Jul 31, 2009 at 12:09 PM, Keenan Tims<[email protected]> wrote: >> then use "time scp /tmp/random otherhost:/tmp/blah" or use "netcat -l -p >> 1234" on one to create a listen and on other "time cat /tmp/random | >> netcat -p 1234 otherhost" to see how long it takes >> > scp doesn't perform well over fast links, it's not really a good tool > for testing. I can barely get 100mbit out of my GigE network that > otherwise performs well. I think it is due to the issue discussed here: > > http://www.psc.edu/networking/projects/hpn-ssh/
Most of the time, the real issue is that scp has to encrypt the data on one end and decrypt it on the other - that takes a lot of CPU power that could otherwise be used for tossing packets around. -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
