Add new Splay benchmark to the V8 benchmark suite and remove...

Add new Splay benchmark to the V8 benchmark suite and remove
the unused parts (most) of the Prototype library from raytrace.js.

Committed: http://code.google.com/p/v8/source/detail?r=1910

[Mads Ager (chromium), 2009-05-12 07:16:02]

LGTM

http://codereview.chromium.org/115227/diff/1/5
File benchmarks/base.js (right):

http://codereview.chromium.org/115227/diff/1/5#newcode37
Line 37: // not accounted for in the benchmark score.
not be

or

are not?

http://codereview.chromium.org/115227/diff/1/3
File benchmarks/splay.js (right):

http://codereview.chromium.org/115227/diff/1/3#newcode65
Line 65: return Math.random();
Maybe we should add a comment here stating that Math.random is deterministic in
the benchmark framework to avoid confusion?

http://codereview.chromium.org/115227/diff/1/3#newcode130
Line 130: 
Remove one space?

http://codereview.chromium.org/115227/diff/1/3#newcode164
Line 164: 
Remove one space?

[Erik Corry, 2009-05-12 07:25:34]

LGTM.

http://codereview.chromium.org/115227/diff/1/5
File benchmarks/base.js (right):

http://codereview.chromium.org/115227/diff/1/5#newcode122
Line 122: window.setTimeout(RunStep, 10);
But why?

http://codereview.chromium.org/115227/diff/1/3
File benchmarks/splay.js (right):

http://codereview.chromium.org/115227/diff/1/3#newcode98
Line 98: else splayTree.remove(greatest.key);
Is there any way we can test whether the splay tree is doing what we expect.  
Eg. test the 0th, 1000th and 3141st elements at the end to see if they are as
expected?

[Erik Corry, 2009-05-12 08:04:16]

LGTM

http://codereview.chromium.org/115227/diff/28/1025
File benchmarks/splay.js (right):

http://codereview.chromium.org/115227/diff/28/1025#newcode104
Line 104: if (keys[i] > keys[i + 1]) {
Shouldn't this be >= if the keys are required to be unique?