On 04/08/2019 13.46, L A Walsh wrote:
On 2019/08/04 04:06, Carlos E. R. wrote:
You haven't shown that it is limiting it to 90% of 1 cpu.
For that, you need to fire up top and observe the load going up and down, but not passing 85% (I set the load limit to 85). See:
your previous example showed it at or near the limit, so I'd expected a similar output like below....
%Cpu(s): 9.4 us, 16.7 sy, 0.0 ni, 72.8 id, 0.1 wa, 0.0 hi, 1.1 si, 0.0 st 19518 root 20 0 91204 4108 1860 R 84.87 0.051 3:32.60 rsyncd .... %Cpu(s): 9.5 us, 17.0 sy, 0.0 ni, 70.1 id, 1.8 wa, 0.0 hi, 1.7 si, 0.0 st 19518 root 20 0 91204 4108 1860 R 85.25 0.051 4:03.47 rsyncd
%Cpu(s): 9.4 us, 19.5 sy, 1.5 ni, 66.4 id, 1.3 wa, 0.0 hi, 1.8 si, 0.0 st 19518 root 20 0 91204 3872 1624 R 84.26 0.048 4:20.53 rsyncd
Yes, the rsyncd process keeps constantly below 85%, it is working correctly.
You have a quad core, I take it?
Right. With program "cpulimit" you can set a limit of 200%, if the process uses more cores. Apparently rsyncd only uses one core. Thus on systemd I wondered if I had to define the limit related to the total number of cores, ie, 20%, or related to 400%. I hit the correct number per chance, at the first try.
Wonder if it can do the same with io & network bandwidth...
:-)
Dunno. I asked google for cpu limit on systemd ;-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)