I have to stop posting active links to our content on Mastodon.
Every time I do so now, it brings down our website for up to 5 minutes.
We've tried pretty much every claimed fix, including third party caching (which in turn breaks other elements of our website's dynamic display abilities), code changes and such on our back end code, and more stuff I don't understand at all (but have spent money paying our WP developer to implement). None of it has worked.
The #fediverse powers that be need to fix this growing problem of the #MastoDDos effect on websites. The more followers and more servers your followers are from, the more impact this has on literally bringing a website to its knees with all the DB calls.
For instance, this morning, I posted the lovely article our creative writer Ethan wrote, which ended up only getting 2 boosts and one "favourite" here, but it brought down our website for 4 minutes and 12 seconds.
That's not sustainable.
@coffeegeek I um... I'm really sorry to say, but it sounds like a skill issue. I assume that you aren't too technical, so you'll have to simply believe me when I say that – it's not normal, you should migrate to another hosting provider and/or publishing technology.
@juandesant just to be clear – same issue being "posting a link to their website on fediverse brings down their website"?
@jonn yes. Every time this user made a blog post, their self-hosted Wordpress-based site was brought down for around five minutes every time they linked to that new post, to the point that they were already telling their audience this would happen, and be patient. And sure enough, after around ~5 min the site would be available again.
@juandesant my comment stands then, there is nothing wrong with getting a 1000 requests per second, computers make like a zillion computations every second, they should be able to... Render HTML based on some DB values *trivially* even under a tenfold load.
@jonn i don’t disagree. What I am saying is that this is a common enough pattern for newcomers to fall into that it might be worth understanding what to do.
@jonn @coffeegeek I know that other people that have tried even to self-host their mastodon servers have had the same issue, so even if it might be the fault of the particular setup, it is something that for those setups always happens.
Mitigating that will also benefit those with better setups, so maybe @Gargron can shed some light on this particular issue.