-
Notifications
You must be signed in to change notification settings - Fork 953
Increase default chunk size for async request #6542
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
Conversation
should we just increase to 128 KB to be consistent with sync? |
| * Default chunk size for Async trailer based checksum data transfer* | ||
| */ | ||
| public static final int DEFAULT_ASYNC_CHUNK_SIZE = 16 * 1024; | ||
| public static final int DEFAULT_ASYNC_CHUNK_SIZE = 64 * 1024; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is only used by legacy code, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the SRA path is already consistent with sync by this change: #6514 . Changed the wording in changelog.
…-sdk-java-v2 into bole/increase_default_chunk_size
|
|
This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one. |



Motivation and Context
According to public S3 documentation, https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-streaming.html , the chunk size is recomended to be at least 64 Kb to achieve better performance. The current default chunk size for sync is 128 KB. With the change in #6514 , the default chunk size for async request using SRA is also 128 KB. However the default chunk size for async for legacy code path is 16 Kb.
Modifications
Increase the DEFAULT_ASYNC_CHUNK_SIZE from 16Kb to 128Kb
Testing
Screenshots (if appropriate)
Types of changes
Checklist
mvn installsucceedsscripts/new-changescript and following the instructions. Commit the new file created by the script in.changes/next-releasewith your changes.License