Implement concurrent downloads and resumable chunked uploads for GCS #31
+84
−19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
The GCS client currently performs single-threaded downloads and uploads, which is inefficient for large files. Additionally, upload failures require retrying the entire file, wasting bandwidth on unreliable networks.
Solution
Concurrent Downloads
Implemented parallel downloads using transfermanager.NewDownloader with 5 concurrent workers and 4MB chunks
Also for encrypted objects falls back to single-stream (transfermanager incompatibility)
Resumable Chunked Uploads
Configured GCS Writer with 100MB chunk size (matching fog-google client). Enables automatic per-chunk retry instead of whole-file retry. Uploads remain sequential (GCS SDK limitation - no NewUploader equivalent)
Chunking provides resumability and memory efficiency, not speed improvement for uploads.