-
Notifications
You must be signed in to change notification settings - Fork 856
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
AWSSDK.CloudFront is slower than AWSSDK.S3 - Signed URL Generation #3130
Comments
@SonalCalcey Good morning. The fix merged in other issue #3122 was made in Thanks, |
Hi @ashishdhingra Good morning. yes, I have a couple of benchmarks using AWSSDK.CloudFront. AWSSDK.CloudFront - 3.7.301.12 AWSSDK.CloudFront - 3.7.300.5 AWSSDK.CloudFront - 3.7.0 All are using AWSSDK.CORE - 3.7.300.19 Thanks, |
@SonalCalcey Thanks for the information. Could you please share sample code to demonstrate what API you are calling to generated signed URL using S3 and CloudFront? Thanks, |
@ashishdhingra These are the sample codes that we used to generate signed URL. Thanks, |
Hi @ashishdhingra, Just to Make sure that you understand the issue we have done a direct benchmark between CloudFront and S3. With the results of the below benchmarks, our main concern is that compared to the S3 signed URL generation time, why the CloudFront signed URL generation time is higher. Is this behavior normal or are there any other methods or ways to get the CloudFront Signed URL without performance degradation that we are unaware of? Benchmark result: Code used for the benchmark:
Versions: AWSSDK.Core - 3.7.300.28 Thanks, |
Describe the bug
Previous issue
Because of the above issue, we are just wondering if there is any issue on the CloudFront as well. Because compared to S3 the CloudFront Response time is x6 or x5 times slower than S3.
These two methods (PlayerSummaryFull and UpdatePlayerProfilePicture) use S3 or CloudFront to Generate Signed URLs.
The Following two benchmark snapshots are by using S3 and CloudFront respectively as media content providers.
AWSSDK.S3 - 3.7.304.7
Benchmark log: Benchmark-using-S3.log
AWSSDK.CloudFront - 3.7.301.11
Benchmark log: Benchmark-using-CloudFront.log
Sorry for not having Multiple version comparisons or more details. The reason for providing these details is FYI to identify if there is any performance degradation on the CloudFront as well.
Expected Behavior
No response
Current Behavior
No response
Reproduction Steps
No response
Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK.CORE - 3.7.300.18
AWSSDK.S3 - 3.7.304.7
AWSSDK.CloudFront - 3.7.301.11
Targeted .NET Platform
.NET Framework 7
Operating System and version
Windows 10 Enterprise
The text was updated successfully, but these errors were encountered: