High constant CPU usage #287
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#287
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm observing a high (+100%) constant CPU usage in my akkoma instance. This is a personal instance, so the activity is mainly due to interactions with other servers.
I'm running the OTP release 3.4.0-0-gf91b89673.
It's a brand new deployment, I've seen another issue regarding CPU usage when migrated from Pleroma develop, but it shouldn't be my case.
In the attached graph, the peak corresponds to a restart of the instance and you can see that it stays at 100% immediately after restarting it.
Ask for whatever you need from logs or phoenix's live dashboard.
Thanks!
You might be able to get
/phoenix/live_dashboard/processes?limit=50&search=&sort_by=reductions_diff&sort_dir=desc
, which should tell you what processes are taking more resources than is usualHi, these are the numbers:
Thanks
nothing seems amiss here
what sort of machine are you running on?
It's a VPS in hetzner with 2xEPYC@2.5GHz, 2GiB RAM and 40GiB SSD.
that should be plenty
do you know which process is taking up the CPU? postgres or beam?
It's the beam. And I see in htop that TIME+ is 349h. May the
systemd restart akkoma
have not actually stopped and started the beam process? Seems strange but... Should I trysystemd stop akkoma
andsystemd start akkoma
instead?that should be fine to do - do the logs show anything curious? systemctl status it
Uhm, I've just checked and it was some other beam process, akkoma related, probably from the setup process as per the cmd I see in ps:
I
kill -15
ed it and the current beam process for the running akkoma instance is back to normal CPU usage <2%.Sorry for the noise! :(
heh, well good that it's back to normal now~