[Shootout-list] X per second scoring system, resume

[Brandon J. Van Every]

Bengt Kleberg wrote:
> Brandon J. Van Every wrote:
> ...deleted
> > Really one would need to do some testing of the target to
> see what the
> > rate of variability actually is.  For a particularly slow-to-start
> > environment, 20 would not be enough.  Like what if some pig language
> > takes 1 second to crank up, that's 5% of your score.  I think GC
> > languages are often piggy like this.  At least, that's my impression
>
> i think that the hello test is neccessary, yes even for the simple
> bechmark, so the user knows about this penalty. for instance,
> if we are
> writing ''reverse'' style utilities.

Sure, but startup/shutdown should be benched explicitly by intent, not
implicitly as fat in tests where it doesn't / shouldn't actually matter.
Interpreted scripting languages are interested in startup/shutdown time.
Compiled number crunching matrix apps are not.  They're going to do a
gazillion things in process, not start/stop processes willy nilly.


Cheers,                         www.indiegamedesign.com
Brandon Van Every               Seattle, WA

20% of the world is real.
80% is gobbledygook we make up inside our own heads.