On Fri, May 09, 2003 at 06:14:19PM +1000, Russell Coker wrote: > On Fri, 9 May 2003 11:44, Martijn van Oosterhout wrote: > > > If I had more spare time I'd make a modification to ssh such that if scp > > > was run as rcp it would use all the usual scp mechanisms for passwords > > > etc, and then just send MD5 signed data through in clear-text after the > > > > I tripled the speed of scp to an old 486SX/33 simply by turning off > > compression. Once I worked that out I added a line to the ssh_config and > > forgot about it. > > Last time I was transferring big files via ssh they were web server log files > and I more than doubled the transfer speed by turning compression on (it > seems that compression takes much less CPU time than encryption). Well, of course. If you're connecting to a webserver, you're presumably going through an Internet-connection, which usually is not that fast. You'll get more through the line, since your connection speed is your bottleneck. If you're connecting to a 486, it does not have enough computing power to keep up with the compression, especially not if you're doing so over an 100Mbit-line. Then, not your connection speed, but your processor is the bottleneck. -- wouter at grep dot be "An expert can usually spot the difference between a fake charge and a full one, but there are plenty of dead experts." -- National Geographic Channel, in a documentary about large African beasts.
Description: PGP signature