-
-
Notifications
You must be signed in to change notification settings - Fork 299
Segmented downloads with multiple connections per file #4498
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
Comments
Segmented download is not the same as multi-connections (#1135) though it does depend on it... With segmented downloads a single large file is downloaded in several parts each using a separate connection. Multiple other download clients now support this - will CyberDuck support this in future? |
lol - this is explicitly NOT the same as #1135! If you don't want to do it that's your prerogative but at least take the time to understand the request! |
https://whatbox.ca/wiki/Multi-threaded_and_Segmented_FTP is a good description of the difference. |
A thumbs up for implementing segmented downloads. |
In efb9fc6. The feature is not currently enabled by default. To enable, set the hidden settings |
Thank you! :) |
Fantastic that the feature is now in the code, thank you so so much. |
As of 9deb42f use the setting
This will add the option Open multiple connections. Use the setting Number of concurrent transfers to control the number of parallel connections. |
Disabled by default in 02ef4f8. Set the hidden configuration option |
Reopen this issue to enable by default and add configuration option. |
Milestone renamed |
Cyberduck does not seem capable of multi-segmenting files in FTP transfer. Consequently, for servers using this method of transfer, files being transferred via Cyberduck do not make full use of bandwidth and transfer far slower than they should. Although I have donated to Cyberduck development because I believe it is a very nice product, I found that for my needs, a product called Speed Download by Yazsoft does provide for multi-segmented transfers at far faster speed.
The text was updated successfully, but these errors were encountered: