I've found that if left on default settings, CloudFlare is not that great at caching. It requires a bit of configuration to really make it sing. itsfoss.com _thought _ they were "using CloudFlare" but probably not to it's fullest potential.
Comment on Please Don’t Share Our Links on Mastodon: Here’s Why! | itsfoss.com
cbarrick@lemmy.world 6 months ago
Just put the site behind a cache, like Cloudflare, and set your cache control headers properly?
rimu@piefed.social 6 months ago
helenslunch@feddit.nl 6 months ago
I’m confused about what is actually causing the load.
Thousands of instances simultaneously fetching link previews from a VPS w/2GB RAM.
cbarrick@lemmy.world 6 months ago
If caching is properly configured, the cache (Cloudflare) will see thousands of requests, but the VPS should only see one request.
tacofox@lemm.ee 6 months ago
This should be front and center, caching won’t be able to make up for that…
breakingcups@lemmy.world 6 months ago
Of course it will, cloudflare is on front of it, they can definitely handje this traffic as long as itsfoss bothers to set correct caching headers for cloudflare to use. That’s the entire point of cloudflare…
Max_P@lemmy.max-p.me 6 months ago
Even without Cloudflare, simple NGINX microcaching would help a ton there.
It’s a blog, it doesn’t need to regenerate a new page every single time for anonymous users. There’s no reason it shouldn’t be able to sustain 20k requests per second on a single server. Even a one second cache on the backend for anonymous users would help a ton there.
They have Cloudflare in front, the site should be up with the server being turned off entirely.