xload.jpg shows what happens to a machine's load after starting up five
cpu-hogging processes, with IQS running.  It was done with "xload -update 1".


IQS currently runs on Solaris 2.x, IRIX, and OSF/1.  It will probably
port easily to anything else having a standard SysV /proc and POSIX signals.


IQS (Implicit Queuing System) is somewhat different from most queuing
systems in use at the time of its writing.

As such, it has its own somewhat unique pluses and minuses.


IQS can be tuned to be more or less aggressive about which processes it picks
for management, and how long its time slices will be.  In the sources:

	FRACTION	A process consumes CPU time "C" in wall clock time "W".
			FRACTION is defined as C/W.
			A process that consumes more than C CPU seconds in
			W wall clock seconds, will be managed by IQS.

	TIME_SLICE	A managed process is allowed to run for this many
			seconds, before potentially being paused for another
			process to run.

We leave these parameters alone tho.


netscape eats a lot of CPU - it's an example of something you might want to
list in /var/IQS/exempt-programs.


I started out writing IQS under linux, but the relevant library had a
memory leak.  So I moved to Solaris, then ported to IRIX and OSF/1.  If
anyone wants to port it to linux now, I'd welcome the contribution.  We
have linux boxes, but none that need IQS.