03-14-2021, 01:07 PM
Update:
Turns out the system doesn't crash. It just gets so slow that updates via the ssh session are measured in minutes instead of milliseconds. At some point the task (git http clone) fails due to a time-out on the HTTPS connection.
From another ssh session I can see that during the git HTTP activity the RAM and swap get hammered before the ssh daemon gets starved and stops updating. Last top output before freeze: 71.8% CPU for NetworkManager, 54.6% for systemd-journal and 54.1% for git-remote-http. Average load is well above 10.
I guess this means that using git on one of these systems is a big nope.
Turns out the system doesn't crash. It just gets so slow that updates via the ssh session are measured in minutes instead of milliseconds. At some point the task (git http clone) fails due to a time-out on the HTTPS connection.
From another ssh session I can see that during the git HTTP activity the RAM and swap get hammered before the ssh daemon gets starved and stops updating. Last top output before freeze: 71.8% CPU for NetworkManager, 54.6% for systemd-journal and 54.1% for git-remote-http. Average load is well above 10.
I guess this means that using git on one of these systems is a big nope.
