Path: utzoo!attcan!uunet!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: comp.arch
Subject: Re: the Multics from the black lagoon :-)
Message-ID: <2121@crdos1.crd.ge.COM>
Date: 12 Feb 90 15:59:34 GMT
References: <8859@portia.Stanford.EDU> <20571@watdragon.waterloo.edu> <49956@sgi.sgi.com> <4791@helios.ee.lbl.gov> <2093@crdos1.crd.ge.COM> <1990Feb7.221800.804@utzoo.uucp> <2106@crdos1.crd.ge.COM> <1990Feb12.053616.11455@Solbourne.COM>
Reply-To: davidsen@crdos1.crd.ge.com (bill davidsen)
Organization: GE Corp R&D Center, Schenectady NY
Lines: 29

In article <1990Feb12.053616.11455@Solbourne.COM> dworkin@salgado.UUCP (Dieter Muller) writes:

| On a single-CPU Series4 Solbourne system:
| 
|     salgado {44} time fastsum /image/os/4.0C/upgrade/USR.tar > /dev/null
|     37.3u 11.4s 0:55 87% 0+648k 4+0io 3612pf+0w
| 
|     salgado {45} time sum /image/os/4.0C/upgrade/USR.tar > /dev/null
|     65.4u 17.0s 1:28 92% 0+184k 3533+0io 3554pf+0w
| 
|     salgado {46} ls -l /image/os/4.0C/upgrade/USR.tar
|     -rw-rw-r--  1 root     29458432 Jan 12 16:15 /image/os/4.0C/upgrade/USR.tar

  This matches very well for the 30-40% I saw on VMS. Considering
another entire type of CPU, o/s, and vendor, I would say it's closer
than I expected. I feel better now saying that there is a gain, and that
it is not 2:1 in most cases.


| Also, the system load average was baselined at 0.45, during fastsum it
| peaked at 0.88, and during sum, it peaked at 1.2.  The significance?
| You tell me.

  I guess I would conclude that it was worth doing in some applications,
and not try to quantify too much. If you do this often I'm sure you
think the effort was well worth it.
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
            "Stupidity, like virtue, is its own reward" -me