Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!RMC.CA!STEVE_LLOYD
From: STEVE_LLOYD@RMC.CA
Newsgroups: comp.sys.apollo
Subject: re: Process Priorities
Message-ID: <901024.10355978.033489@RMC.CP6>
Date: 24 Oct 90 15:02:43 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20

Thanks John - I've never really understood why that happens.  The effect
is even more dramatic on a single board unit.

In research solutions to the problem I came across a product called NQS
(Network Queing System, I think).  This is a batching facility for Unix
machines that has been ported to the DN10k. It has very elegant partioning
and priorities.  It won't get rid of the non-aging problem but will allow
you to keep the number of jobs running to a low enough number that the
machine won't do it's nose dive to 2%.  With user cooperation you could
keep 1 queue running with several non swapping jobs and have a different
queue where the swappers would be forced into one at a time.  It certainly
isn't the best solution since the software costs real money, but it's
better than having a DN10k performing like a DN3000.

Unfortunately I can't find the advertising bumff on the product -
It's lost in a very disorganized pile of stuff.
I know that it was developed by NASA and is marketted by one of
their subcontractors - that narrows it down to about half the contractors
in the US.  If you're interested I'll look it up.  Perhaps someone else
out there has the info at their finger tips?