CPU Usage on recently migrated instance #265
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#265
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?
Heya!
Great project, I wish I found this before going on a Pleroma -> Soapbox -> Pleroma migration journey. I noticed a very high CPU usage running the dev-version of Akkoma. I needed it to migrate from Pleroma dev, only when switching to the stable branch it fell. Network was me prewarming the media cache (that seems to have never worked with Pleroma, hence the rise in traffic).
Both Akkoma setups ran in production mode of course.
ah you've run into this issue
this should fix it for you -> https://docs.akkoma.dev/develop/installation/migrating_to_akkoma/#warning-migrating-from-pleroma-develop
I ran those (from akkoma develop branch) successfully, that was the reason I was on the development branch - but while on there, it was hogging a bit more CPU than I'd like.
has it fallen back to normal by now?
Switching back to the stable branch, recompiling and restarting: Yes.
This issue was intended as a "Hey, sth might be up with whats coming in develop" hint :)
i run on develop, can't say i've seen any behaviour like this on it
there are unknown issues moving from pleroma develop though, that's more likely to be the cause tbh
k :)
if this does hit you again when next stable is released, any chance you could grab whatever is at
/phoenix/live_dashboard/processes?limit=50&search=&sort_by=reductions_diff&sort_dir=desc
?that should tell you if anything is acting weird