Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!inuxc!pur-ee!uiucdcs!uiucdcsm!grunwald
From: grunwald@uiucdcsm.UUCP
Newsgroups: comp.arch
Subject: Re: Gould NP1
Message-ID: <3300002@uiucdcsm>
Date: Sat, 4-Apr-87 14:12:00 EST
Article-I.D.: uiucdcsm.3300002
Posted: Sat Apr  4 14:12:00 1987
Date-Received: Sun, 5-Apr-87 22:06:00 EST
References: <505@sw1e.UUCP>
Lines: 11
Nf-ID: #R:sw1e.UUCP:505:uiucdcsm:3300002:000:563
Nf-From: uiucdcsm.cs.uiuc.edu!grunwald    Apr  4 13:12:00 1987


Queuing theory isn't reality, though. I'm runing CSIM-based simulations on
an Encore multimax. We have 10 CPUs. I can grab 4 or 5 of them in the
middle of the day and still leave plenty for everyone else.
	I can run a single job on each CPU, and I never block. I never
context switch except for paging. I avoid the overhead of having to swap
between processes & the comensurate clearing of my working set from
memory.
	When you have a set of 70 -> 150 simulations to run & you have to
put up with a time-sharing system, there's alot to be said for multiple
CPUs.