Skip to content
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

Throttle Transfers #11997

Closed
cyberduck opened this issue Dec 13, 2005 · 2 comments
Closed

Throttle Transfers #11997

cyberduck opened this issue Dec 13, 2005 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Dec 13, 2005

cfa3ec0 created the issue

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.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 27, 2006

@dkocher commented

Milestone 2.7 deleted

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 22, 2007

@dkocher commented

In be6fca2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants