Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!nike!oliveb!epimass!jbuck
From: jbuck@epimass.UUCP (Joe Buck)
Newsgroups: net.arch
Subject: Re: Floating point performance
Message-ID: <531@epimass.UUCP>
Date: Thu, 16-Oct-86 12:56:14 EDT
Article-I.D.: epimass.531
Posted: Thu Oct 16 12:56:14 1986
Date-Received: Thu, 16-Oct-86 23:41:27 EDT
References: <340@euroies.UUCP> <1989@videovax.UUCP> <722@mips.UUCP> <8184@sun.uucp> <8575@lanl.ARPA>
Reply-To: jbuck@epimass.UUCP (Joe Buck)
Organization: Entropic Processing, Inc., Cupertino, CA
Lines: 18
Summary: Mflops/MHz == flops per cycle

In article <8575@lanl.ARPA> jlg@a.UUCP (Jim Giles) writes:
>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-)

You multiplied instead of dividing.  If you had divided, you would
have found that the number measures floating point operations per
cycle.

-- 
- Joe Buck 	{hplabs,fortune}!oliveb!epimass!jbuck, nsc!csi!epimass!jbuck
  Entropic Processing, Inc., Cupertino, California