The results are in, after seeing about 800 boosts on the post to see how the Mastodon embed actually affects our server load. Here's what happened....basically nothing for us.
@gamingonlinux There’s a lot missing here. How many CPU cores? Is this normalized load? What was the latency? Were there timeouts? Why are you looking at ~10 minute intervals when the reported problem is with spikes of ~1 minute? Very “works on my machine” type post
@gamingonlinux Sorry, didn’t mean to be mean. I was concerned that you were using your platform to show that this isn’t a problem without understanding what the problem is.
When a link is posted on an account that’s federated to a lot of instances, it gets accessed many times all at once to generate link previews. That means you should see very short bursts of traffic, and that can be enough to cause requests to queue up and possibly time out or get rejected. Hope that helps
@gamingonlinux it's kinda funny that instead of hiring someone to submit a patch for their issue, #itsfoss decided to publish the article about their technical problems
The article reads superficial, like vague request for commercial proposal but for free lol
> #Mastodon instance admins, please fix our computer, or else we'll stop reposting to your social network
@graphito "just hire someone" is not really a valid thing here though for smaller sites, the article framing was poor given how heavy their site is but the issue behind it does exist
@gamingonlinux I think itsfoss doesn't have proper caching set up for their CDN and just gets bombarded with every request for the site, possibly every subsequent request by every user as well.
@chris as a dynamic site too, we also don't exactly use a plain html cache either, but our website is also around 1mb without browser cache on an article, there's is like 11mb!
Add comment