Instability investigation #1
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
@theoryshaw asked me to look into the poor performance of this instance.
Looking at the admin dashboard, I couldn't spot anything abnormal (the memory Garbage Collection might be a bit too high, but nothing conclusive).
Logging in with ssh, it appears that the vm was "swaping" (storing parts of the memory on disk instead of RAM, which usually results in poor performance). After running
sudo swapoff -a && sudo swapon -a
, the swap was cleared:To deter linux from using the swap too soon, I also reduced the vm.swapiness to
10
(from its default value of60
), by editing/etc/sysctl.conf
and reloading the settings withsudo sysctl --system
.The current value can be checked with
sysctl vm.swappiness
(orcat /proc/sys/vm/swappiness
), which now both output10
.A couple of minutes later, the swap is being used again:
Trying to find the process responsible for swap usage:
So mariadb seems to go easily to swap.
The theorical RAM usage of mariadb does not seem too high:
A bit later, the swap is being used even more, but mainly by the
gitea
process:Use the
GOMEMLIMIT
env var to try to reduce RAM consumption of Forgejo. In/etc/systemd/system/gitea.service
, adjust theService
Section:The instance has been upgraded to an instance with 4GB of RAM (instead of 2GB). The DNS were updated accordingly.
The
/etc/systemd/system/gitea.service
file has been adjusted toGOMEMLIMIT=2000MiB
.