Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site ea.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!inuxc!pur-ee!uiucdcs!ea!mwm
From: mwm@ea.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Automatic Nice'ing of Processes
Message-ID: <13500028@ea.UUCP>
Date: Tue, 18-Dec-84 13:51:00 EST
Article-I.D.: ea.13500028
Posted: Tue Dec 18 13:51:00 1984
Date-Received: Fri, 21-Dec-84 02:02:48 EST
References: <359@mddc.UUCP>
Lines: 20
Nf-ID: #R:mddc:-35900:ea:13500028:37777777600:828
Nf-From: ea!mwm    Dec 18 12:51:00 1984

/***** ea:net.unix-wizards / ukma!sean /  6:47 pm  Dec 14, 1984 */
It seems to me a simple solution would be to remove re-niceing and write a
daemon to renice cpu hogs. The main advantage of this would be that you
would have complete control of what gets reniced.

Sean
/* ---------- */

Bingo. I've started one of these beasts already, having been inspired by
the VMS "thumper" that does just that. I think the correct name for the
thing is "external scheduler", and consider it as a replacement for the
long-term half of the Unix scheduler (on the off chance that Unix actually
has a long-term scheduler).

Should you have source (lucky devils), this approach is silly. You would
be better off rewriting the Unix scheduler. The daemon could be used to
testbed different versions of the scheduler under load, though.