Question

A batch data-processing service named crunch.service is starving interactive workloads on a shared server by consuming excessive CPU. You need a persistent configuration that limits crunch.service to at most 40% of one CPU core, using systemd's native resource control and surviving reboots and package updates. Which approach best accomplishes this?

Accepted Answer

Run 'systemctl edit crunch.service', add 'CPUQuota=40%' under a [Service] section, then run 'systemctl daemon-reload' and restart the service

Answer

Add 'nice -n 19' to the ExecStart line in the vendor unit file at /usr/lib/systemd/system/crunch.service and restart the service

Answer

Run 'renice +19 -p $(pidof crunch)' after each boot to lower the process priority

Answer

Add 'CPUShares=40' to a drop-in file and reboot the system