Question

Bad CDN performance

Posted July 30, 2021 87 views
CDN

Hey! We are experiencing issues with CDN performance.
We use spaces to keep static files for our web app.
We tried several times, with several browsers, each time is after the fresh deploy - which means all static files are new, were just uploaded to bucket and CDN cache was purged right after that.

And there is a delay in 40-60 seconds in chrome and chromium for new CDN files (browser show files as pending).
The only firefox works fine.
Our whole team experience that and we’re all over the world.

Any ideas, what might be wrong?

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.

×
Submit an Answer
1 answer

I have made one small experiment. Uploaded two new files and with https://tools.pingdom.com measured the response time from the different locations.
I did that in order from top to bottom, from left to right.
So for js I see that origin server is faster than CDN endpoint, actually.
And for the picture, I see that it takes some time (several minutes!) to actually be uploaded across CDN network.
Is that how it suppose to be?

https://opsjet-nft-prod.sfo2.digitaloceanspaces.com/9464-c06fa574727719d41c59.js

europe, frankfurt
cdn: 1.68s; 2.09s
origin: 2.25s; 2.19s

europe, london
cdn: 2.88s; 2.86s
origin: 1.97s; 2.07s

north america, washington
cdn: 2.47s; 1.45s; 2.00s; 2.58s
origin: 1.63s; 1.47s; 1.47s; 1.47s

https://opsjet-nft-prod.sfo2.digitaloceanspaces.com/img.jpg

europe, frankfurt
cdn: 1.70s; 1.70s; 61ms
origin:1.48s; 1.45s; 1.46s

europe, london
cdn: 1.67s; 44ms (!); 56ms
origin:1.36s; 1.30s; 1.34s

na, washington
cdn: 908ms; 46ms; 59ms
origin: 685ms; 692ms; 693ms