Scheduling priority for the 'nice' command
I'm trying to run seti@home on my RedHat 8 Linux box but I'm having trouble achieving the results I want.
I'm trying to duplicate the results I get on Windows. There I run seti@home with 'idle' priority. The result of this is that the CPU usage from seti@home drops to basically 0% when another hard crunching process with normal priority kicks in for a long while.
Now, I tried the same (or so I think) in Linux. I launched seti@home with:
nice +19 ./seti
However if I check the CPU time used by the seti process it hovers at around 8% even when another normal process that would otherwise need ~100% of the CPU time is running.
Is there a trick that I'm missing?