Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(236)

Side by Side Diff: chrome/test/data/third_party/spaceport/README.md

Issue 10154006: Add test data for spaceport benchmark. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 8 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
(Empty)
1 Basic benchmarks to measure HTML5 performance and support for game related featu res
2
3 Running the Tests
4 -----------------
5
6 1. Install [Node.js][1] (0.6.0+).
7 2. Run in shell: `npm install`
8 3. Run in shell: `node server`
9 4. Open in browser: `http://localhost:3002/`
10 5. Configure parameters of the test run, if desired.
11 6. Click "Run Tests".
12 7. If you uploaded results, see the `server/uploads/` directory.
13
14 [1]: http://nodejs.org/
15
16 Interpreting Results
17 --------------------
18
19 ### Sprite tests
20
21 The `Source type` indicates the data being displayed.
22
23 The `Technique` indicates the browser method used to render the data.
24
25 The `Test type` indicates what transformations were performed on the data using
26 the technique.
27
28 The `JS time (ms)` result shows how much JavaScript time was spent rendering
29 the objects in one second.
30
31 The `Objects at 30FPS` result shows how many objects were able to be rendered
32 while rendering at 30 frames per second.
33
34 ### Audio latency test
35
36 The `Cold play latency` indicates how much time it took between `.play()` and
37 the first subsequent `play` or `timeupdate` event on a new WAV `<audio>`
38 element.
39
40 The `Warm play latency` indicates how much time it took between `.play()` and
41 the first subsequent `play` or `timeupdate` event on a WAV `<audio>` element
42 which has already played.
43
44 ### Canvas text test
45
46 The `Score` result shows how many renders could be made per 100 milliseconds.
47
48 Code structure
49 --------------
50
51 Test cases are build into a recursive object structure. Test cases are run
52 through the test runner in `js/testRunner.js`.
53
54 Test cases are displayed based upon the specification in `js/tables.js`.
55
56 ### Sprite tests
57
58 Sprite tests are found under `js/sprites/`.
59
60 There are three interleaved components:
61
62 #### Sources
63
64 Each source represents some asset (e.g. a sprite sheet). Maps to the `Source
65 type` result.
66
67 #### Transformers
68
69 Transformers modify the source by applying affine or other transformations.
70 Maps to the `Test type` result.
71
72 #### Renderers
73
74 Renderers displayed transformed sources using different techniques. Maps to the
75 `Technique` result. See `js/sprites/renderers/README.md` for details.
OLDNEW
« no previous file with comments | « chrome/test/data/third_party/spaceport/README.chromium ('k') | chrome/test/data/third_party/spaceport/assets/html5-logo.png » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698