Question

DO Spaces Request timing is slow - basic images load slowly, poor performance.

  • Posted December 1, 2018
  • CDN

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.

Subscribe
Share

Submit an 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.

To Digital Ocean admins: it’s a shame to let many users complaining about a basic paid service that obviously does not work, without bringing any answer. It shows a lack of transparency about your infrastructure issues, a lack of customer support (stop trying to hide issues by saying “please open a ticket”), and will lead to people to migrate to AWS or GCS. Just saying…

To Digital Ocean admins: it’s a shame to let many users complaining about a basic paid service that obviously does not work, without bringing any answer. It shows a lack of transparency about your infrastructure issues, a lack of customer support (stop trying to hide issues by saying “please open a ticket”), and will lead to people to migrate to AWS or GCS. Just saying…

Same here. Slow performance. I think I made an mistake choosing Spaces.

Same problem here. Small jpg images (~250 KB) take quite long to load (~ 1s).

Even I can confirm the same. Our 480P videos served from DO CDN do not load at all.

I have the same problem all the images load very slowly

I’m suffering the same.

I’m using DO Spaces CDN configuration and I don’t know the origin of the problem, but requests that contains assets of image type are unseemly slow.

A little real example of a request:

image1.jpeg 249 KB --> 5.41 s image2.jpg 279 KB --> 3.94 s image3.svg 818 B --> 2.20 s image4.svg 1.5 KB --> 2.13 s image5.svg 1.6 KB --> 2.13 s image6.svg 997 B --> 1.88 s

Configuration:

DROPLET in AMS3 location STORAGES in AMS3 location

Can anyone explain this bad beaviour?? I’m very frustrated.

Like many others, we also have a new Space in AMS3 and retrieval is indeed slow. Like, really slow, several seconds for a 200 kb PNG.

However! Once CDN was enabled, it became absolutely lightning fast, even for the first time it was opened. We are using it for audio files and images, usually under 1 MB.

Because files are already fast for the very first time they are loaded, it seems Spaces automatically pushes them out to the CDN, without having to first hit the storage origin server (like on Cloudflare).

It seems Spaces wasn’t really designed for end-user access without CDN, so if you are distributing URLs pointing directly to your Spaces, you must to have CDN enabled.

Looks like this has been an issue since 2019 which is greatly concerning as a new customer who is noticing how slow this is already.

I agree, was testing origin vs cdn endpoints, I’m not sure they are even configured correctly.

A small image from nyc to denver will take 500->600ms, thats just plain slow even for non cdn, cdn link will maybe take 300ms at best. Thats pretty poor performance. Same image from fastly/keycdn, ~16ms. Yes 16ms!! I would be more forgiving, but DO has a POP IN Denver! So I would expect 30-60ms at best.

I don’t have the resources to move off of spaces right now, but jees, you really need to improve infrastructure, we’re going to have to put imgix or fastly in front of their cdn to get any sort of acceptable caching.