Personally I read it as an X/Y problem thing. It taking 2.5 minutes to run is bad because during those 2.5 minutes, the CPU is so busy that other programs freeze up. If the script didn't freeze up the computer, it taking 5 or even 10 minutes might be more acceptable.
| [reply] |
run faster, not slower
Well, you could read it like have the rest of the programmes run nicer to make the important one faster.
However, the nice(1) command may modify niceness both ways, so you can indeed use it to prioritize a single process.
Still, with the process in question already clogging all available cpu, I wonder if it is any help at all.
Cheers, Sören
Créateur des bugs mobiles - let loose once, run everywhere.
(hooked on the Perl Programming language)
| [reply] |
I'm not sure what your point is. I replied to a comment that specifically suggested lowering the priority.
And sure, one could use it to increase its priority, but that's not what the comment suggested, and I doubt it would help.
| [reply] |
I replied to a comment that specifically suggested lowering the priority.
...of processes. You misread that as lowering the priority of the OP's programme.
Otherwise, we have no argument.
Cheers, Sören
Créateur des bugs mobiles - let loose once, run everywhere.
(hooked on the Perl Programming language)
| [reply] |