Comment 32 for bug 1972159

Description of problem:

Systemd-oomd is very aggressive when it comes to memory management. In fedora 33 I've been able to run quite a few apps without a problem but in fedora 34, the apps get killed way too quickly. Here's an example of atom getting killed by systemd-oomd:

Mar 20 22:18:34 x505za systemd-oomd[1020]: Memory pressure for /user.slice/user-1000.slice/user@1000.service is greater than 10 for more than 10 seconds and there was reclaim activity
Mar 20 22:18:34 x505za systemd[1604]: app-gnome-atom-11930.scope: systemd-oomd killed 47 process(es) in this unit.
Mar 20 22:18:36 x505za systemd[1604]: app-gnome-atom-11930.scope: Deactivated successfully.
Mar 20 22:18:36 x505za systemd[1604]: app-gnome-atom-11930.scope: Consumed 7.557s CPU time

This event is triggered when around 70-80% of my memory is filled up despite still having space in swap.

Version-Release number of selected component (if applicable): systemd 248 (v248~rc4-1.fc34)

How reproducible:
Always

Steps to Reproduce:
1. Load up a bunch of apps to fill up memory
2. Wait for systemd-oomd to trigger reclaim activity
3.

Actual results:
Apps get killed very quickly

Expected results:
Apps to run normally until memory and swap is almost full

Additional info:

System Specs:

Ryzen 3 2200u
4GB RAM
Kernel 5.11.7-300.fc34.x86_64