@BuddyTheBeefalo@lemmy.ml to Fediverse@lemmy.worldEnglish • 1 year agoPlease Don’t Share Our Links on Mastodon: Here’s Why! | itsfoss.commastodon.socialmessage-square41fedilinkarrow-up193arrow-down144
arrow-up149arrow-down1external-linkPlease Don’t Share Our Links on Mastodon: Here’s Why! | itsfoss.commastodon.social@BuddyTheBeefalo@lemmy.ml to Fediverse@lemmy.worldEnglish • 1 year agomessage-square41fedilink
minus-square@helenslunch@feddit.nllinkfedilinkEnglish10•edit-21 year ago I’m confused about what is actually causing the load. Thousands of instances simultaneously fetching link previews from a VPS w/2GB RAM. https://mastodon.social/@itsfoss/112369476450719989
minus-square@cbarrick@lemmy.worldlinkfedilinkEnglish15•1 year agoIf caching is properly configured, the cache (Cloudflare) will see thousands of requests, but the VPS should only see one request.
minus-square@tacofox@lemm.eelinkfedilinkEnglish0•1 year agoThis should be front and center, caching won’t be able to make up for that…
minus-square@breakingcups@lemmy.worldlinkfedilinkEnglish26•edit-21 year agoOf course it will, cloudflare is in 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…
Thousands of instances simultaneously fetching link previews from a VPS w/2GB RAM.
https://mastodon.social/@itsfoss/112369476450719989
If caching is properly configured, the cache (Cloudflare) will see thousands of requests, but the VPS should only see one request.
This should be front and center, caching won’t be able to make up for that…
Of course it will, cloudflare is in 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…