Performance Degradation and Increased Allocation in AWSSDK.S3 Versions 3.7.107.4 and Above

[SonalCalcey]

Describe the bug

We have identified a performance degradation in our API after updating the AWSSDK.S3 package to the latest version 3.7.304.1.
Upon investigation, we have identified that performance degradation is occurring after the AWSSDK.S3 version 3.7.107.4.

Furthermore, we have done a Benchmark test for the AWS SDK.S3 versions such as

• 3.7.107.3
• 3.7.107.4
• 3.7.304.1

To help you better understand the issue, we have prepared a sample description highlighting the key observations and differences.

Expected Behavior

Expected to have similar performance and allocation rate for as AWSSDK.S3 - 3.7.107.3 after the Nuget package update.

Current Behavior

(Benchmark results were taken using BenchmarkDotNet v0.13.10)

Summary for the AWS SDK.S3 3.7.107.3

Benchmark log: s3-sdk-3.7.107.3-benchmark.log

Summary for the AWS SDK.S3 3.7.107.4

Benchmark log: s3-sdk-3.7.107.4-benchmark.log

Summary for the AWS SDK.S3 3.7.304.1

Benchmark log: s3-sdk-3.7.304.1-benchmark.log

Reproduction Steps

Code used for the Benchmark:

Possible Solution

No response

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

AWSSDK.S3 - 3.7.107.3
AWSSDK.S3 - 3.7.107.4
AWSSDK.S3 - 3.7.304.1

Targeted .NET Platform

.NET Framework 7

Operating System and version

Windows 10 Enterprise

[ashishdhingra]

Perhaps issue #3116 is similar.

[ashishdhingra]

Discussion here

[SonalCalcey]

The issue is kind of similar to this #3116, but each signed URL generation has a high memory allocation rate as well.

[afroz429]

Thanks for the reporting the issue and taking time to pinpoint the exact version where the performance degradation started. These details were very helpful in identifying the root cause. The issue was with the AWSSDK Core and we resolved it in 3.7.300.18. The latest nuget packages already shipped with this fix.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.