Xref: utzoo comp.arch:6057 comp.lang.prolog:1179
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!ucla-cs!admin.cognet.ucla.edu!casey
From: casey@admin.cognet.ucla.edu (Casey Leedom)
Newsgroups: comp.arch,comp.lang.prolog
Subject: Re: Perils of comparison -- an example
Message-ID: <15221@shemp.CS.UCLA.EDU>
Date: 14 Aug 88 04:38:06 GMT
References: <282@quintus.UUCP>
Sender: news@CS.UCLA.EDU
Reply-To: casey@cs.ucla.edu.UUCP (Casey Leedom)
Organization: UCLA
Lines: 16

In article <282@quintus.UUCP> ok@quintus () writes:
> 
> ... kLI/s are defined solely by that particular benchmark, by the way.
> Other benchmarks may be "procedure calls per second", but _only_ Naive
> Reverse gives "logical instructions".

  I believe "kLI/s" is 1000's of Logical Inferences per second (but I may
be wrong of course).  This is normally abrieviated as kLIPS.  Really fast
PROLOG machines are rated in mLIPS (10^6 LIPS).

  LIPS is a logical analog to the floating point FLOPS metric.  Note that
both LIPS and FLOPS are useful measures while MIPS is of debatable use -
at least until the industry can standardize the measure and stop gloming
a system's entire performance profile into a single number.

Casey