You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to throttle individual connections. For example, if I have to upload 100M+ of stuff, I'd like to throttle this so that it doesn't hog all of the office's outgoing bandwidth. This capability is present in rsync, and via solutions like trickle, but it would be nice to see it in Cyberduck.
I'm not sure what the best interface would be for this feature, but it should have a visible indicator so that people don't turn it on and then wonder why things are slow. Perhaps a "Throttle" or "Speed Limit" item in the Action pulldown, producing a dialog with boxes for maxiumum upstream and downstream consumption. These values could then be displayed in the status bar, perhaps in red.
I suggest it as a per-connection feature for two reasons: 1) A global option would probably generate bogus bug reports from users who set it and then forgot about it; 2) I may have one mammoth upload (or download) that I want to perform while still getting good performance on other, smaller transfers to and from other servers.
The text was updated successfully, but these errors were encountered:
It would be nice to be able to throttle individual connections. For example, if I have to upload 100M+ of stuff, I'd like to throttle this so that it doesn't hog all of the office's outgoing bandwidth. This capability is present in rsync, and via solutions like trickle, but it would be nice to see it in Cyberduck.
I'm not sure what the best interface would be for this feature, but it should have a visible indicator so that people don't turn it on and then wonder why things are slow. Perhaps a "Throttle" or "Speed Limit" item in the Action pulldown, producing a dialog with boxes for maxiumum upstream and downstream consumption. These values could then be displayed in the status bar, perhaps in red.
I suggest it as a per-connection feature for two reasons: 1) A global option would probably generate bogus bug reports from users who set it and then forgot about it; 2) I may have one mammoth upload (or download) that I want to perform while still getting good performance on other, smaller transfers to and from other servers.
The text was updated successfully, but these errors were encountered: