On Tue, 2007-03-13 at 16:17 -0500, Sunny wrote:
On 3/13/07, John Andersen
wrote: I think you will find that on local networks where nothing is less than 100meg that ssh is quite a bit slower than a well tuned nfs.
As you said the magic word "well tuned nfs" ... :)
Please, define well-tuned. Or direct me to a very nice tutorial for this. I found a bunch all over the place, and I have very bad experience with the nfs performance while writing to nfs volumes. Very often it stops the transfer for some seconds, konqeror reporting "Stall" and then resumes. The last part of the file usually takes along time, etc. These observations are made using konqueror, midnight commander, and pure cp from commandline. Sometimes even the overall responsivness of the machine is lost (and this is 3400+ amd with 2G).
The files in question are usually more than 300M, and they start pretty well, but after the first 50-70 MB it starts to stall. I found out that using sftp takes about the same amount of time, but does not hog the mouse movement or window switching, as nfs write does.
I would suspect that this has to do with file system caching. The file won't be saved to disk straight away, but to memory. When the memory fills up, it will flush to disk. Does it make a difference if the box has just been rebooted compared to when the box has been up and running for a while? The sftp would be a bit slower generally as it is encrypted, so the target machine will not be hammered, thus being able to flush to disk without you noticing.
-- Svetoslav Milenov (Sunny)
Cheers, Magnus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org