2
Problem has improved, but is not gone (midwest.social)
submitted 2 years ago by seahorse@midwest.social to c/main@midwest.social
3 comments fedilink hide all child comments

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.

top 3 comments
sorted by: hot top controversial new old
[-] Arindrew@midwest.social 1 points 2 years ago

Has the influx of new members exacerbated this issue? I found this thread because I'm seeing a few '504 Gateway Timeout' errors occasionally.

[-] seahorse@midwest.social 1 points 2 years ago

Beehaw is also noticing these issues. It's most likely from the influx of new users.

[-] pelotron@midwest.social 1 points 1 year ago* (last edited 1 year ago)

Any updates on server stability lately? I've been having a lot of connectivity issues the last couple days, and just saw this post on lemmy.world that was pretty interesting.

@seahorse@midwest.social have you been dealing with performance problems like this?

(side note, how do you embed a link to another instance that will let midwest.social users stay logged on?)

this post was submitted on 21 Dec 2022
2 points (75.0% liked)

main

1349 readers
4 users here now

Default community for midwest.social. Post questions about the instance or questions you want to ask other users here.

founded 3 years ago
MODERATORS
seahorse@midwest.social