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

[S3 Storage] Obey throughput limit configuration #647

Merged
merged 1 commit into from
Sep 19, 2023

Conversation

rzvoncek
Copy link
Contributor

Fixes #611.

@sonarcloud
Copy link

sonarcloud bot commented Sep 19, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Copy link
Contributor

@adejanovski adejanovski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Brilliant!

@@ -136,6 +136,12 @@ def connect(self):
tcp_keepalive=True
)

self.trasnfer_config = TransferConfig(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: typo

@@ -136,6 +136,12 @@ def connect(self):
tcp_keepalive=True
)

self.trasnfer_config = TransferConfig(
# we hard-code this one because the parallelism is for now applied to chunking the files
max_concurrency=4,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: we should make that a constant

@adejanovski adejanovski merged commit c45c94a into master Sep 19, 2023
27 checks passed
@rzvoncek rzvoncek deleted the radovan/s3-throughput branch September 22, 2023 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Post S3 backend revamp: handle throttling
2 participants