Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site tove.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!mcnc!philabs!cmcl2!seismo!umcp-cs!tove!mark
From: mark@tove.UUCP (Mark Weiser)
Newsgroups: net.unix-wizards
Subject: Re: Off-loading processes to an idle machine
Message-ID: <164@tove.UUCP>
Date: Sat, 23-Mar-85 20:08:04 EST
Article-I.D.: tove.164
Posted: Sat Mar 23 20:08:04 1985
Date-Received: Tue, 26-Mar-85 06:24:45 EST
References: <248@unc.UUCP> <5714@ucbvax.ARPA>
Reply-To: mark@tove.UUCP (Mark Weiser)
Organization: U of Maryland, Laboratory for Parallel Computation, C.P., MD
Lines: 17
Summary: ...Maryland does it routinely for troff's

In article <5714@ucbvax.ARPA> dcmartin@ucbvax.UUCP (David C. Martin) writes:
>In article <248@unc.UUCP> menges@unc.UUCP (John Menges) writes:
>>I'm studying the problem of attempting to off-load
>>non-interactive processes from one machine intended
>>to be used primarily for interactive work for many
>>users to another machine intended to run non-interactive jobs.

We do this routinely at Maryland for troff's.  When the load goes
above a certain level all troff's on the high load machine are shipped
for remote execution to one of several machines (depending on which is up).
Generally, the users don't know the difference.  Steve@Maryland, 
who wrote most of the code, can say more.
	-mark
-- 
Spoken: Mark Weiser 	ARPA:	mark@maryland	Phone: +1-301-454-7817
CSNet:	mark@umcp-cs 	UUCP:	{seismo,allegra}!umcp-cs!mark
USPS: Computer Science Dept., University of Maryland, College Park, MD 20742