Add spaceport benchmark to Chrome Remote Control.

chrome/test/data/third_party/spaceport/js/tests/sprites.js

Index: chrome/test/data/third_party/spaceport/js/tests/sprites.js
diff --git a/chrome/test/data/third_party/spaceport/js/tests/sprites.js b/chrome/test/data/third_party/spaceport/js/tests/sprites.js
index b491fe6a5cd4718be1d0c110fc4d86ca59013e15..64b2d03b24140e36d412234e3057494ad7001db7 100644
--- a/chrome/test/data/third_party/spaceport/js/tests/sprites.js
+++ b/chrome/test/data/third_party/spaceport/js/tests/sprites.js
@@ -168,7 +168,7 @@ define([ 'sprites/sources', 'sprites/transformers', 'sprites/renderers', 'util/e
                 rawData.push([ objectCount, results ]);
                 
                 var timePerObjectEstimate = 1/(objectCount*results.fps);
-                var estimatedMaxObjects = Math.floor(1/(targetFramerate * timePerObjectEstimate));

[nduca, 2012/11/04 19:53:30]

should we be editing the README.chromium to notate this edit?

[tonyg, 2012/11/05 23:02:01]

Done.

+                var estimatedMaxObjects = Math.min(5000, Math.floor(1/(targetFramerate * timePerObjectEstimate)));
                 

[nduca, 2012/11/04 19:53:30]

shouldn't we switch from having a real checkout of spaceport to using a wpr
recording? I have this feeling we're doing it wrong if not...

[tonyg, 2012/11/05 23:02:01]

There are a few reasons it is checked in:
1. Spaceport isn't hosted anywhere online to record from.
2. There are a couple of local modifications which are easier to track this way
than in a recording.
3. Currently android is using this checked in version downstream (but that can
change).

                 var nextObjectCount = nextNumberToTry(fpsResults, estimatedMaxObjects);
                 test(nextObjectCount);