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

Queued transfers do not respect the global upload speed when starting #5335

Closed
cyberduck opened this issue Oct 18, 2010 · 2 comments
Closed

Queued transfers do not respect the global upload speed when starting #5335

cyberduck opened this issue Oct 18, 2010 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Oct 18, 2010

quaqsim created the issue

  1. Set the upload bandwidth preference to 5KiB/s
  2. In the Transfer window, set the maximum number of simultaneous uploads to 1
  3. Start a transfer that will take a minute or two to upload
  4. Queue a second transfer that is big enough to allow the speed to be recognisable
  5. Before the first transfer ends, set the upload bandwidth preference to 10KiB/s
  6. The first transfer will continue uploading at 5KiB/s

  7. Note that when the first transfer finishes, the second will start but continue using 5KiB/s

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 20, 2010

@dkocher commented

Are you changing the bandwidth option in Preferences → Bandwidth or for the particular transfer in the Transfers window?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 20, 2010

@dkocher commented

Bandwidth rates are read from the preferences at the time the transfer is created. If it is queued, it is expected that the old setting will apply.

@cyberduck cyberduck closed this Nov 20, 2010
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant