-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance of download #55
Comments
Your example runs in about 40-50 seconds for me, which is still pretty slow. I noticed that after sending the packet, it takes anywhere from 2-4ms to get the first response data, but sometimes it spikes up to 42ms, which seems suspiciously slow. I'll dive into more debugging as soon as I get some more time. |
I digged a bit deeper and can reproduce that it sometime takes longer than 40ms to read(). |
While trying to reproduce the issue, I noticed that it is no longer relevant and seems to have been resolved in Eugeny/russh#412. At this point, the download speed in your example is about 54 MBps, which is roughly the same as the WinSCP client speed of around 56.8 MBps |
I am not sure if I am doing something wrong but the download speed is way slower than it could be. I am trying to fetch a 1GiB file from my local vm as a testcase. The vm is just a freshly setup debian 12 with only openssh installed.
This is what I am doing:
After tweaking the values a bit I get roughly 60-70 MBps:
without doing anything I get only 10 MBps 😵💫 :
A quick test with the sftp command line:
Is this the expected performance? Or did I do something wrong? 🤔
I also did a quick cross check using a go library and this one is very close to what the sftp command line is doing:
The text was updated successfully, but these errors were encountered: