I ran a test on the same image across DO block storage [e.g. basic web server $10/mo tier], DO Spaces, and AWS S3.
The results confirm what I’ve been seeing: DO Block loaded image in 0.41s DO Spaces loaded image in 1.25s AWS S3 loaded image in 0.49s
It appears that the lag is the request portion of the load timing [Connect -> Request -> Response -> Dom… etc]. Connect and response timings appear faster than block storage.
I’m just really confused as to why anybody is using Spaces at this point – on a normal webpage it has noticeable lag across images. I’ve also been using as asset storage for Craft CMS and the images in backend UI take forever to load, nothing I’ve ever noticed with block or S3.
Question is does DO acknowledge this service is generally slow? Not intended for web usage and intended for something else? I’ve read the optimization guide, and it does mention to avoid small files, but it begs to question what in the world is any web developer using Spaces for? We need fast delivery of lots of little files. I really would like an alternative to AWS S3 bundled into the beautiful and function DO backend. If DO Spaces is not going to be fast please stop advertising it as CDN an alternative to S3.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.