You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(deps): Update module github.com/aws/aws-sdk-go-v2/feature/s3/manager to v1.22.0 (#22029)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [github.com/aws/aws-sdk-go-v2/feature/s3/manager](https://redirect.github.com/aws/aws-sdk-go-v2) | require | minor | `v1.21.1` -> `v1.22.0` |
---
> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
---
### Configuration
📅 **Schedule**: Branch creation - "before 3am on Saturday" (UTC), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate).
// If we don't use a reader that supports seeking, the S3 SDK will allocate a 5MB buffer each time it reads a chunk
29
-
// While this can work for large files, it's not optimal for small files, based on our tests we're mostly uploading small files
30
-
// And depending on source concurrency and destination batch settings, we can upload quite a bit of small files at the same time
31
-
// For example we've seen 220 concurrent uploads where most files are only a few dozen KB, this means we're allocating ~1GB of memory, where we could be allocating only a few MBs
32
-
// The memory is only cleared after the upload is finished, which makes it even worse
33
-
// Please note that for large files the memory we read is capped by the batch size setting which defaults to 50MB
// We don't use a reader that supports seeking if NoRotate is set since that means we'll be holding the entire file in memory until the table has finished resolving and the file is uploaded.
36
-
// This has the downside of potentially using a lot of memory for tables with small files.
37
-
// But it's a tradeoff we're willing to make for now until https://github.com/aws/aws-sdk-go-v2/issues/2694 is resolved, as it has a workaround that we can use (reducing source concurrency).
0 commit comments