Subj : Re: Replacing SM with Rhino
To   : netscape.public.mozilla.jseng
From : celso
Date : Fri Jan 14 2005 05:23 pm

A more realistic approach to benchpress.js
is to consider % of time independently for
each test to avoid assigning weights where
they don't or should not exist. Also, some
of the tests were yielding less than 1 ms
results, which didn't mean much (they were
probably done for computers slower than what
they are today). In this case SM comes out
faster, close to what was described before
by Igor.
Thanks,

Celso

Benchpress(v3) in JavaScript...
benchmark		time (ms)	% time
Engines->		SM	R-JIT	SM	R-JIT
AtAllPutBenchmark	31	78	0.284	0.715
BounceBenchmark		15	94	0.137	0.862
BubbleSortBenchmark	235	172	0.577	0.422
IncrementAllBenchmark	62	93	0.4	0.6
MMIntBenchmark		16	32	0.333	0.666
MMFloatBenchmark	15	31	0.326	0.673
NestedForLoopBenchmark	219	156	0.584	0.416
NestedWhileLoopBenchmar	250	156	0.615	0.384
PermBenchmark		125	157	0.443	0.556
QueensBenchmark		78	93	0.456	0.543
QuicksortBenchmark	78	79	0.496	0.503
RecurseBenchmark	110	156	0.413	0.586
SieveBenchmark		125	78	0.586	0.384
StorageBenchmark	62	78	0.442	0.557
SumAllBenchmark		32	47	0.405	0.594
SumFromToBenchmark	234	203	0.535	0.464
TakBenchmark		250	203	0.551	0.448
TaklBenchmark		1891	953	0.664	0.335
TowersBenchmark		421	485	0.464	0.535
TreeSortBenchmark	141	250	0.36	0.639
total			4390	3594	9.07	10.88
ratio					1	1.2

.