Nice Performance Tuning For UNIX

Professor writes "Be 'nice' to your computers and examine some general guidelines for tuning server performance. A computer is like an employee who does tasks for you -- it's a good idea to keep from overburdening them. Keep this from happening by using the UNIX 'nice' command."

Comments

Re:what about killall

[LLuthor]

Umm. You can't sigkill init on Linux (at least on moderately recent kernels). I am pretty sure that is also the case on BSD systems.

Yep ...
In arch/i386/kernel/signal.c [2.6.17-rc1-mm2]

563 /*
564 * Note that 'init' is a special process: it doesn't get signals it doesn't
565 * want to handle. Thus you cannot kill init even with a SIGKILL even by
566 * mistake.
567 */
568 static void fastcall do_signal(struct pt_regs *regs)

Re:what about killall

[Stradenko]

The above post refers to the killall from the psmisc package.

The Sun Solaris "killall" command kills *all* processes.

AIX "killall" kills all processes (except those in its family tree) owned by the calling user (maybe owned by the calling user *and* attached to the current terminal...).

Re:Worst. Advice. Ever.

[gowen]

Then, instead of finishing during the early morning hours, it lasts all day, interferring with real work.

If there are no other processes competing for resources, niced and non-niced processes will complete in approximately the same time. If your niced late-night updatedb is taking forever, its because you've chosen to run other processes overnight as well. And if your updatedb runs quickly, then the other processes will "interfere with real work".

In short : nice doesn't change the total amount of time your processes take (or, at least, not by very much), it just changes which one finishes first.