What is the limit on sshd connection? How much data can it process?
Tell me more
×
Server Fault is a question and answer site for
professional system and network administrators. It's 100% free, no registration required.
closed as not a real question by Zoredache, Chris S♦, John Gardeniers, theotherreceive, splattne♦ Aug 3 '10 at 13:01
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, see the FAQ.
|
The bandwidth of your connection is going to be the primary determining factor on the rate of data transfer. Otherwise, you could do some comparative testing. If you mean some limit on the total, I don't think there is one. What is it that you're trying to do? What problem are you trying to solve? |
|||||||
|
|
If the question you're trying to ask is "why is my SCP slow" or "how can I make SCP/SFTP transfers faster", you'll want to look into the HPN-SSH patch here: http://www.psc.edu/networking/projects/hpn-ssh/ Newer versions of OpenSSH do have larger buffers that fix some of the speed issue on high-latency high-throughput connections, but not all of it. The HPN-SSH patches also add the 'NoneSwitch' option, which allows you to encrypt the authentication but not the transfer itself. This will save keep you from bottlenecking on the CPU for high-speed transfers. Of course, you'll only want to use that switch if you don't need to encrypt the data. Also, if you're using the -C (compression), don't. It tends to bottleneck rapidly on a single CPU over anything but a pretty slow link. If you have multiple cores, it may be worth using something like pigz (multithreaded gzipper) or tamp (multithreaded lzo.. a bit easier on the CPU than gzip). |
|||
|
|
