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

Upload big files directly to S3 #276

Merged
merged 3 commits into from
Jul 19, 2019
Merged

Upload big files directly to S3 #276

merged 3 commits into from
Jul 19, 2019

Conversation

Keats
Copy link
Contributor

@Keats Keats commented Jul 18, 2019

No description provided.

@Keats Keats changed the title Vp big files s3 Upload big files directly to S3 Jul 18, 2019
Copy link
Contributor

@polyatail polyatail left a comment

Choose a reason for hiding this comment

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

This looks good! Do we have to distinguish between compressed and uncompressed files?

The way the CLI works right now, FASTXPassthru will upload files however they are--compressed or uncompressed--and let the proxy uncompress them (if necessary) and recompress them. In contrast, FASTXInterleave will always uncompress, interleave, and upload the files uncompressed. The self._fsize attribute is actually the uncompressed size of both files summed together in FASTXInterleave and the file size on disk for FASTXPassthru. Both self._fsize are the actual file sizes that will be uploaded.

We probably don't have to guess that a 50GB compressed file will be uploaded as some larger amount: FASTXInterleave._fsize is the actual uncompressed file size already and FASTXPassthru._fsize is the file size that will be uploaded.

@Keats
Copy link
Contributor Author

Keats commented Jul 19, 2019

Ah you're right, we can probably have just one number then!

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.0009%) to 83.814% when pulling 90245fd on vp_big_files_s3 into 287f7a5 on master.

@polyatail polyatail merged commit 6037fed into master Jul 19, 2019
@polyatail polyatail deleted the vp_big_files_s3 branch July 19, 2019 21:43
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.

None yet

3 participants