CPU Usage on recently migrated instance #265

Closed
opened 2022-11-11 14:39:03 +00:00 by tim · 7 comments

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.

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
Author

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.

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?

has it fallen back to normal by now?
Author

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 :)

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

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
Author

k :)

k :)
tim closed this issue 2022-11-11 14:56:34 +00:00

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

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
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#265
No description provided.