Subject: Re: TCP gurus: explain this ssh hang...
To: None <firstname.lastname@example.org>
From: Todd Whitesel <email@example.com>
Date: 01/09/2000 01:46:56
> Beats me, but I don't think you'll find ssh acceptable for your purpose,
> because some bug in the F-secure/"OpenSSH" client code (and possibly in
> the server as well, but I'm fairly sure at this point it's in the client)
> limits throughput, even with "cipher none", to about 2.5MB/sec on loopback.
It'll do for now. My jobs are effectively very compute bound because the
clients are so slow.
My ssh-based setup is about maxed out now, and I get very acceptable speedups
already (sun3 GENERIC builds in 2.5 hours instead of 8, for example). Tonight
I am taking a final set of performance numbers, and then I'm going to try a
variant of rsh that spoofs stderr a little to return the exit code properly.
Probably I will ditch ssh for a completely different reason. I need to be
root on the client, but I really don't like coming in as root on the server.
ssh -l doesn't like me, su+ssh takes forever, but rsh -l works and is fast.
toddpw @ best.com