@gamingonlinux There’s a lot missing here. How many...

All posts Liam @ GamingOnLinux 🐧🎮's posts Post Back to profile

@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

Like 2 May at 11:13 | Wall-to-wall | Open on jorts.horse

4 comments

Liam @ GamingOnLinux 🐧🎮

@grampajoe You could try being a bit nicer ya know, this kind of reply in future will just get you muted, this is just the charts my host gives me 🤷

2 May at 12:22 | Open on mastodon.social

Grampa

@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

2 May at 13:14 | Open on jorts.horse

Liam @ GamingOnLinux 🐧🎮

@grampajoe I've never said it isn't a real problem that exists, I just wanted to do a basic test for myself to see and it was fine, nothing more

2 May at 13:52 | Open on mastodon.social

Grampa

@gamingonlinux I guess I’m trying to say it might not have been fine, because it might not show up as a high load average. If you have server logs (especially proxy logs e.g. nginx) from the time you posted the link, you might see what I’m talking about. The concern I have is that people will see this and think it’s evidence there isn’t a problem given the reach your posts are getting.

2 May at 14:22 | Open on jorts.horse