Problem has improved, but is not gone
Problem has improved, but is not gone
The high CPU issue that is causing midwest.social to slow way down and timeout on HTTP requests is still a mystery to me. But, it seems to do it less often and for less time now.
Here is CPU usage over 24 hours:
It's a bunch of SELECT statements in Postgres that all seem to fire at one time and take a while to complete as a batch. I've inspected the logs and haven't seen anything unusual. Just stuff federating and posts receiving upvotes.
You're viewing a single thread.
Is this issue still ongoing? I've had various threads that I've had issues accessing via Jerboa and the pwa on my Chromebook. Can't figure out if it's a Lemmy-wide issue or instance-specific... from 404 issues to the website hanging when I submit a post along with pages that only load the header
I've been having timeout and 404 issues since I created my account last week. Typically can't browse more than 5 minutes before I start getting timeouts, which can last for several minutes to several hours before anything loads again. Thought it was a gerboa issue at first, but I'm using a browser now and getting them too.
Unfortunately it still happens, just not nearly as often as it used to. Need to meet up with my database admin to get to the bottom of the issue.
