From Fedora Project Wiki
No edit summary |
mNo edit summary |
||
| Line 23: | Line 23: | ||
* Now run the test: | * Now run the test: | ||
<pre> | <pre> | ||
systemd-run --user --scope /usr/bin/stress-ng --brk | systemd-run --user --scope /usr/bin/stress-ng --brk 2 --stack 2 --bigheap 2 --timeout 90s | ||
</pre> | </pre> | ||
* Make sure to clean up the override and reset the test unit when you're done: | * Make sure to clean up the override and reset the test unit when you're done: | ||
| Line 33: | Line 33: | ||
* The system becomes unresponsive during the test but should respond again once `stress-ng` is killed. | * The system becomes unresponsive during the test but should respond again once `stress-ng` is killed. | ||
* If the main `stress-ng` was killed, the command will print "Killed" and a non-zero exit code. If it runs to completion, it say something about "successful run" and exit 0. | * If the main `stress-ng` was killed, the command will print "Killed" and a non-zero exit code. If it runs to completion, it say something about "successful run" and exit 0. | ||
* systemd-oomd will have killed all the processes before the | * systemd-oomd will have killed all the processes before the timeout. `stress-ng` may take some time to build up pressure. If the the command runs to timeout, it means systemd-oomd did not kill it. | ||
* You can verify by checking for some of the relevant log lines with `journalctl`: "Memory pressure for <...> and there was reclaim activity" or "systemd-oomd killed <...> process(es)" | * You can verify by checking for some of the relevant log lines with `journalctl`: "Memory pressure for <...> and there was reclaim activity" or "systemd-oomd killed <...> process(es)" | ||
}} | }} | ||
Revision as of 07:52, 18 March 2021
Description
This test case tests that systemd-oomd will kill a cgroup with the most pgscans when memory pressure on user@$UID.service exceeds 10% (or whatever was defined in systemd-oomd-defaults).
Setup
- This test case should be performed on either bare-metal or virtual machines.
- Check that you are running systemd 248~rc1 or higher with
systemctl --version. - Ensure the systemd-oomd-defaults package is installed (included with Fedora 34).
- You will also need to install
stress-ng. - Boot the system and log in as a regular user.
- So as not to trigger the swap policy for systemd-oomd, create an override with the following commands (don't forget to remove this file and
systemctl daemon-reloadto restore the settings afterwards):
sudo mkdir /etc/systemd/system/-.slice.d/ printf "[Slice]\nManagedOOMSwap=auto" | sudo tee /etc/systemd/system/-.slice.d/99-test.conf sudo systemctl daemon-reload
How to test
- Check that systemd-oomd is running:
systemctl status systemd-oomd
- Check that the systemd-oomd-defaults policy was applied by running
oomctland verifying that "/user.slice/user-$UID.slice/user@$UID.service/" is listed as a path under "Memory Pressure Monitored CGroups" along with some stats. "Swap Monitored CGroups" should show no paths since we put in an override. - Now run the test:
systemd-run --user --scope /usr/bin/stress-ng --brk 2 --stack 2 --bigheap 2 --timeout 90s
- Make sure to clean up the override and reset the test unit when you're done:
sudo rm /etc/systemd/system/-.slice.d/99-test.conf sudo systemctl daemon-reload
Expected Results
- The system becomes unresponsive during the test but should respond again once
stress-ngis killed. - If the main
stress-ngwas killed, the command will print "Killed" and a non-zero exit code. If it runs to completion, it say something about "successful run" and exit 0. - systemd-oomd will have killed all the processes before the timeout.
stress-ngmay take some time to build up pressure. If the the command runs to timeout, it means systemd-oomd did not kill it. - You can verify by checking for some of the relevant log lines with
journalctl: "Memory pressure for <...> and there was reclaim activity" or "systemd-oomd killed <...> process(es)"