By mrmooky
I spend some time this morning setting up my first Space and already moved a bunch of files into my bucket. As location, I choose SFO3. To my understanding, the CDN will automatically check my location and give me the files from the server closest to me, right? I upload to the base bucket and DO CDN takes care of the rest, distributing and such.
Btw, I‘m using my own subdomain. I have the same files in a bucket directly with AWS S3, with the location in Frankfurt, Germany. When using DigitalOcean to retrieve instantsearch.js, the file takes about 2s to load. Using my „old“ S3, the same file takes very few milliseconds. This is probably due to the location of the file, which is much closer to me.
2s for a js file is way too long. I assume the CDN is not working as expected, or am I missing something? It seems I retrieve the files from the SFO location, although I assumed the CDN would pick the Frankfurt location, which is closer to me and supported by the DO CDN, according to the docs.
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!
Heya,
Just came across this answer and decided to write some general guidelines for anyone who comes across this in the future despite the old question.
First, ensure that your CDN is enabled for your Space, and you are using the CDN endpoint (e.g., https://your-space-name.nyc3.cdn.digitaloceanspaces.com) rather than the base endpoint.
Regarding the file retrieval from different locations, the CDN should indeed distribute your content to edge locations closer to your users. Please note that the origin of the files remains at the actual location of the Space, and having a Space located geographically closer to the majority of your visitors can also affect the performance.
A CDN improves download performance by caching content in multiple locations globally. The time it takes the cache to populate in a particular region can vary, hence there’s potential for some latency when a file is fetched for the first time. If the problem continues, consider reaching out to DigitalOcean support for more assistance.
For more details on how the CDN feature works in DigitalOcean Spaces, you may refer to this guide.
Hope that this helps!
Hi there,
A quick update here on the CDN Spaces side!
We’ve massively expanded our Spaces Content Delivery Network (CDN), now boasting approximately 274 Points of Presence (PoPs) globally.
This upgrade significantly boosts speed and reliability for web applications, ensuring a smooth and swift experience for users everywhere.
This introduces a reduced latency, enhanced performance, and the added bonus of SEO advantages, at no extra cost.
Best,
Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
