Every time I post a link to my site on Mastodon, it locks up for like 30 seconds or so.
My theory is that because I have a quite a lot of followers (👋 hii!) the post hits a lot of instances and they all poll my site at the same time, effectively DDoS'ing it for a lil bit.
One day I'll run a packet capture and prove this theory…
@kev I see the same thing. My little raspberry pi’s cpu spikes up every time I post a link, but it isn't too bad. I have fewer followers than you though 😅
@dustinrue Ohhhh this is useful, thanks. I have considered a move behind Cloudflare in the past, for exactly this reason, but CF makes me feel icky. So I’ve jsut kinda put up with the ~30seconds downtime when something is posted.
I only serve my font files from my CDN. I should fix that…
@mauricerenck I do. I prefer not to use plugins when I can help it. I do use caching in Kirby, but it’s the basic file cache that comes bundled. I’ll check out Staticache though.
@picofarad@dustinrue This spawned a thought…I checked the head of my site for where the favicon and “feature-image” is being served from. I thought this was my CDN, but it wasn’t, it was local.
I’ve now changed that to my CDN, so we will see if that fixes the issue next time a link is posted. Thanks.
@LexPendragon The problem isn’t people visiting, it’s a mastodon thing. Whenever a link is posted, Mastodon polls the site to pull things like a feature image, and some other meta data. This, as I understand it, is so Masto can display the card.
I have around 26k followers, so let’s say that’s over 500 instances. That’s 500 servers, all making requests to my lil server at the same time.
@mms Problem is, Mastodon doesn’t provide a referrer (and rightly so) so doing a tail on the logs after the fact won’t really help. I’ll just see a load of IPs.
That’s why I’d like to do a pcap, as it would show a spike in real-time.
Add comment