I have been running with this configuration this week, and have been running a script to log occurrences of my memory and swap usage each exceeding 90%. I have had several such occurrences, but have yet to experience any noticeable performance issues. For example, this morning `oomctl` reported the following usage, but I was able to continue using my system without any noticeable difference:
> $ cat /etc/systemd/ system/ -.slice. d/10-oomd- root-slice- defaults. conf
> [Slice]
> ManagedOOMSwap=auto
I have been running with this configuration this week, and have been running a script to log occurrences of my memory and swap usage each exceeding 90%. I have had several such occurrences, but have yet to experience any noticeable performance issues. For example, this morning `oomctl` reported the following usage, but I was able to continue using my system without any noticeable difference:
$ oomctl user-1000. slice/user@ 1000.service
Memory Pressure Limit: 50.00%
Pressure: Avg10: 0.00 Avg60: 0.00 Avg300: 0.00 Total: 6s
Current Memory Usage: 13.5G
Memory Min: 0B
Memory Low: 0B
Pgscan: 13490147
Last Pgscan: 13490147
Dry Run: no
Swap Used Limit: 90.00%
Default Memory Pressure Limit: 60.00%
Default Memory Pressure Duration: 20s
System Context:
Memory: Used: 14.3G Total: 15.5G
Swap: Used: 979.9M Total: 979.9M
Swap Monitored CGroups:
Memory Pressure Monitored CGroups:
Path: /user.slice/
This is just one data point of course, but it puts me in favor of disabling swap kill for Jammy.