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

Allow S3Transfer config to be customised #676

Closed
wants to merge 1 commit into from

Conversation

michalc
Copy link

@michalc michalc commented Mar 2, 2019

A typical use for this would be to control number of threads, or even disabling threads. For example, some transfers are unlikely to be faster than the transfer to/from S3, and so triggering threads is unlikely to be helpful.

The setting AWS_S3_TRANSFER_CONFIG is used twice so that S3Boto3Storage and S3Boto3StorageFile, which can be used directly in client code, can both be customised.

@michalc michalc force-pushed the s3-transfer-config branch 5 times, most recently from 6cc1a82 to 419f2ab Compare March 2, 2019 07:16
A typical use for this would be to control number of threads, or even
disabling threads. For example, some transfers are unlikely to be faster
than the transfer to/from S3, and so triggering threads is unlikely to
be helpful.

The setting AWS_S3_TRANSFER_CONFIG is used twice so that S3Boto3Storage
and S3Boto3StorageFile, which can be used directly in client code, can
both be customised.
@michalc michalc force-pushed the s3-transfer-config branch from 419f2ab to 8fdb7a1 Compare March 2, 2019 07:37
@sww314 sww314 added the s3boto label May 10, 2019
@jschneier
Copy link
Owner

Superseded by #1280. I guess 4 years later is better than never...

@jschneier jschneier closed this Aug 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants