-
Notifications
You must be signed in to change notification settings - Fork 34
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
Don't reset rclone rate limit when not needed #4119
Comments
Michal-Leszczynski
added a commit
that referenced
this issue
Nov 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rclone server has
globalConfigGuard
that should update rate limit / transfers used by the agent only when the update is actually changing the value. Otherwise, we perform unnecessary re-initialization, which might be costly.Here are logs from an SCT test running 2 backups and restore:
We can see that rate limit has been updated multiple times, even though there was no need for it.
In the implementation we can see:
We simply forgot to update the value cached in
globalConfigGuard
after setting it withcore/bwlimit
call.The text was updated successfully, but these errors were encountered: