https://bugs.kde.org/show_bug.cgi?id=495441
--- Comment #3 from Dominik Kummer <ad...@arkades.org> ---
INFO:
For now I use this:
Exec=systemd-run --user --slice=intense.slice kdevelop
with my custom desktop file.
Additional coding fun fact:
I've set my PATH environment to "/home/me/bin:/usr/bin" and put the following
make-wrapper into `/home/me/bin`:
--
#!/bin/bash
# Check if the script is being run as root
if [ "$EUID" -eq 0 ]; then
# Run make within a systemd slice with --pipe to pass output directly
systemd-run --quiet --same-dir --slice=build.slice --wait --pipe /bin/make
"$@"
else
# Run the command normally if already in user context
systemd-run --quiet --same-dir --user --slice=build.slice --wait --pipe
/bin/make "$@"
fi
--
now my 12 core workhorse system is perfectly balanced. Heavy build jobs run in
a build.slice which forbids swap usage.
app.slice and intense.slice run perfectly smooth and responsive with high cpu
priority on swap during builds now.
This kind of resource management is more powerful than expected.
--
You are receiving this mail because:
You are watching all bug changes.
