Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!hp4nl!maestro!hanst
From: hanst@maestro.htsa.aha.nl (Hans Trompert)
Newsgroups: comp.sys.sequent
Subject: Re: Dynix load average
Message-ID: <880@maestro.htsa.aha.nl>
Date: 8 May 89 08:28:53 GMT
References: <2470@helios.ee.lbl.gov> <67727@pyramid.pyramid.com>
Sender: hanst@maestro.htsa.aha.nl
Reply-To: hanst@htsa.UUCP (Hans Trompert)
Organization: AHA-TMF (Technical Institute), Amsterdam The Netherlands
Lines: 19
To: comp.sys.sequent

In article <67727@pyramid.pyramid.com> csg@pyramid.pyramid.com (Carl S. Gutekunst) writes:
>In article <2470@helios.ee.lbl.gov> Jef Poskanzer <jef@helios.ee.lbl.gov> writes:
>>(I haven't tried it on a heavily loaded system yet because I
>>haven't managed to get the load average above 1.6...)
>There's a reason for that. Dynix divides the load average by the number of
>CPUs you have. If uptime(1) displays 1.6, and you have four CPUs, then the
>load average is really 6.4.
If you want a GOOD load average, try a parallel make with 50 source files
(the nethack sources will do fine), that will do the trick !!
On our Sequent (Balance 8000 with 8 CPU's) it results in a load average above
10.0. The only problem is the size of your swap space, you run quickly out
of memory. Try it and have fun ?!!