Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!caip!clyde!cbatt!ihnp4!inuxc!iuvax!bobmon
From: bobmon@iuvax.UUCP (Robert Montante)
Newsgroups: net.arch
Subject: Re: Floating point performance
Message-ID: <1661@iuvax.UUCP>
Date: Fri, 17-Oct-86 13:02:20 EDT
Article-I.D.: iuvax.1661
Posted: Fri Oct 17 13:02:20 1986
Date-Received: Sat, 18-Oct-86 23:07:01 EDT
References: <340@euroies.UUCP> <1989@videovax.UUCP> <722@mips.UUCP> <8184@sun.uucp> <8575@lanl.ARPA>
Organization: Indiana University, Bloomington
Lines: 27
Summary: some more dimensional analysis

>>                            Mflops Per MHz
>>   [...]
>Mflops:(Millions of FLoating point OPerations per Second)
>MHz: (Millions of cycles per second)
>
>Therefore 'Mflops per MHz':(Millions^2 FLoating point OPeration cycles per
>			    sec^2)
>
>Sounds like an acceleration to me.  Must be a measure of how fast computer
>speed is improving.  Still, the choice of units forces this number to
>be small.      8-)

I get:     10e6  X  FLoating_point_OPerations / second
         -----------------------------------------------
           10e6  X  Cycles / second

which reduces to
                 FLoating_point_OPerations / Cycle

an apparent measure of instruction complexity.  But then, if you use a Floating
Point Accelerator, perhaps these interpretations are consistent.  8->

*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*-=-*

RAMontante
Computer Science				"Have you hugged ME today?"
Indiana University