Summary: | kio_sftp is much slower than command line scp | ||
---|---|---|---|
Product: | [Unmaintained] kio | Reporter: | Todor Buyukliev <todor> |
Component: | sftp | Assignee: | Andreas Schneider <asn> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | a, alessandro-ghersi, alpha_one_x86, alvaro.aguilera, david, kernelcruncher, muziofg, senjas, vojta.d, xia_nai |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Use sftp_async_read to speed up get requests |
Description
Todor Buyukliev
2009-12-15 15:01:56 UTC
The reason is that the old kio implementation and the current sftp implementation in libssh is a blocking IO. We are working on this so you have to wait for the next libssh version. *** Bug 218845 has been marked as a duplicate of this bug. *** *** Bug 219532 has been marked as a duplicate of this bug. *** *** Bug 245204 has been marked as a duplicate of this bug. *** *** Bug 239824 has been marked as a duplicate of this bug. *** Created attachment 51758 [details]
Use sftp_async_read to speed up get requests
The attached patch uses sftp_async_read to speed up the sftp kioslave. Preliminary testing showed that the transfer speed locally increased from ~3MByte/s to 18-20 MByte/s.
It should apply cleanly to trunk (r1152597) but was developed against the KDE 4.5 branch.
Let me know if there are any issues with the patch and I will try to fix them.
Philip: Thank you very much for your patch! I haven't implemented this yet cause we plan to have complete async API in libssh 0.5. I think the concept will be much the same how to use it. So it makes probably sense to apply it now. I will talk to Aris how the API should look like in libssh 0.5, review your patch carefully and come back to you. *** Bug 253430 has been marked as a duplicate of this bug. *** *** Bug 246557 has been marked as a duplicate of this bug. *** *** Bug 240814 has been marked as a duplicate of this bug. *** 4.6.1 is still infected with the issue. *** This bug has been confirmed by popular vote. *** *** This bug has been marked as a duplicate of bug 254865 *** |