What are the differences between loading a page using CDN and what kind of prodivers are you using? I have much longer loading time to use with cdn. Can I do something wrong or don’t know about something ? maybe i should still set some settings I don’t know about?

Well, the first clue … thanks to . A little bit. How much? We’re talking about days, weeks? Should we force a payload in https or rather http ? I’m asking because there are differences in loading. What does it depend on whether the page is loaded all or looks like the original javascript would have not been loaded ??

The time frame will depend on how the users interact with the site. The most downloaded assets will get loaded to the CDN caché, and will be faster if you’re closer to the CDN server than from the server. If you have the datacenter next to you, and the CDN server is 1000Km away, it will always be slower. The idea of the CDN is to serve better a geographically diverse audience, not to improve centralized visits.

But are we talking about a situation once we add the cdn address to our app.yml file or not ? And what is the reason to use a subdomain for cdn addres? i.e. why can’t it be DISCOURSE_CDN_URL: //637763234.cdn-provider.com and should be discourse-cdn.example.com ??

[image] marianord: The time frame will depend on how the users interact with the site. Yes, I know, but I’m checking with different testing tools from many regions of the world. And cdn is always slower !

Are you talking about TTFB on which path exactly? TTFB for a static asset (like a JS file, or a JPG user upload) will always be fast using a CDN, as latency only of the multiple PoP will help with it. TTFB of dynamic routes in the other hand makes no sense to compare, as our DISCOURSE_CDN_URL doesn’t cover those anyway.

[image] Falco: on which path exactly? Can you explain exactly what you mean ? I’m giving the results for the test forum. (btw it’s just come out a little faster) // But it’s only on a fresh domain without content. [image] and for the cloudfront created [image]

What you are seeing is just normal variance. CDN will have no impact on the time to first byte on your the root of your Discourse instance or in any other dynamic route. A CDN will only serve the static assets.

And is there a difference if these resources (static assets) are kept in S3 ?

No, there’s none. The CDN will cache those assets from S3 when needed. [image] eextra: And what is the reason to use a subdomain for cdn addres? That is just a vanity address, is not needed at all.

First Byte Time vs CDN?

Development

pfaffman (Jay Pfaffman) February 18, 2020, 2:51pm 2

CDN will be slower until it gets resources cached. You might wait a while before doing any testing.

Topic		Replies	Views
How to solve super slow loading time for site? Self-hosting	8	3798	August 12, 2023
The initial page load Site feedback	20	9681	November 6, 2015
Optimizing Site For Speed - How To Improve? Development	13	888	April 6, 2024
New beta update has noticeably slowed initial load time with a reverse proxy? Product Support	7	855	July 16, 2019
Does CDN make sense for private forum using SSO? Product Support	2	577	January 17, 2022

First Byte Time vs CDN?

Related topics