Conversation
Notices
-
Back to its old tricks.
Снимок экрана_20240401_194140.p…
-
I'll just change the CPU governor to powersave so that the fan hum would stop driving me insane. Then it could run at 100% CPU usage however long it wants.
-
@munir No point, they work fine. It's a software issue.
-
@mint Oil the fans maybe
-
@munir My instance has been up for almost two years and is running on an underpowered hardware (although I've done a bit of work to speed some things up). That said, the issues started cropping up only last week.
-
@mint I dunno why pleroma is shitting itself on your server constantly, on mine i barely have 1% cpu usage, but then again this is single user instance
-
@munir Mine is proxied to a VPS via Wireguard.
-
@mint I do wonder how people manage to run services and shit from their home networks, Leased Internet Lines are so damn expensive
-
@mint @munir
I do the same, except with tinc.
-
@munir @mint wazzap
-
Decreased max_worker_processes to 3, CPU is still hammered a bit, but at least there's been no 500s in the last 15 minutes or so. Also it looks like the scrobble endpoint has been timing out quite often, so I nooped it in nginx for now. The long 15 seconds queries as seen in phoenix dashboard are likely timelines; maybe I should modify the frontend to hammer them less often, and add some rate limiting.
-
Very tempted to add some RLIMIT_CPU limit to postgres container.
-
I'll reboot the whole system in a minute, just in case.
-
Now Beam is also shitting itself.