Possible higher memory usage due to timeouts #331
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#331
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?
Saw this in my server monitoring today. Typically memory usage is quite flat, but here we have some nice bumps. Luckily it didn't swap or OOM, but I checked from the logs and they're filled with messages such as:
I think we had some request queued up in the memory, timing out eventually. I do not know why the timeouts happened, but if similar thing would happen with a larger server, this could mean a crash due OOM.
Also CPU usage peaked a lot during this.