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
I am using this amazing package to host my website media on S3 bucket, everything went okay except the performance of retrieving images has become slower. I did a quick comparison, by measuring the loading time retrieving a local image and retriving the same image using S3 and Virtual Path Provider.
The comparasion:
Retrieving image from S3 bucket
Local Image
I investigated for this issue, and I found S3 provides another EndPoint which is faster : something.s3-accelerate.amazonaws.com, but I didn't know how this can be used and configured, because the documentation here says I don't need to add Bucket HostName since I am using Virtual Path Provider.
Please advice for this.
The text was updated successfully, but these errors were encountered:
It would be relatively easy to enable the S3 Accelerate endpoint. We'll have to add a new web.config key for it as S3 Accelerate isn't enabled on buckets by default.
I'll do some testing in the next week and look at adding this.
Also sorry I ignored this for 2 months - I didn't get an email notification and I don't check Github that often. Will try to check more regularly!
I am using this amazing package to host my website media on S3 bucket, everything went okay except the performance of retrieving images has become slower. I did a quick comparison, by measuring the loading time retrieving a local image and retriving the same image using S3 and Virtual Path Provider.
The comparasion:
Retrieving image from S3 bucket
Local Image
I investigated for this issue, and I found S3 provides another EndPoint which is faster :
something.s3-accelerate.amazonaws.com
, but I didn't know how this can be used and configured, because the documentation here says I don't need to add Bucket HostName since I am using Virtual Path Provider.Please advice for this.
The text was updated successfully, but these errors were encountered: