386668 - Add additional performance test suites to talos

Status: RESOLVED INCOMPLETE

(Release Engineering :: General, defect)

Description

[Mike Schroepfer]

Besides Tp/Ts/memory we need to augment our testing infrastructure with tests that stress different parts of the browser.   Such as:

http://wiki.mozilla.org/Mozilla2:Trender
http://dev.jquery.com/~john/slickjq/
http://bubblemark.com/
http://trac.webkit.org/projects/webkit/wiki/JavaScript%20and%20DOM%20Benchmarks
http://www.howtocreate.co.uk/browserSpeed.html
http://www.quirksmode.org/dom/innerhtml.html
http://xkr.us/bench/tables.html

We can look into borrowing some of these or creating our own new synthetic benchmarks.  Ideally we'd develop a set of tests which each individually stress a particular part of the system so we can better understand the cause of improvements or regressions in the bigger benchmarks.

Comment 1

[Mike Schroepfer]

Some more sources of benchmarks:

http://www.extremetech.com/article2/0,1697,2152778,00.asp

Interesting technique to test actual page render time (by capturing video):

http://www.hanselman.com/blog/VideoWindowsBrowserSpeedShootoutIE7Firefox2Opera9SafariForWindowsBeta3.aspx

Some synthetic JS benchmarks.  Try/Catch benchmark is questionable but the math, DOM, Array, and String functions look reasonable:

http://celtickane.com/projects/jsspeed.php

Comment 2

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Found during triage. 

Alice: are there some specific test suites here that we should add to Talos?

Comment 3

[alice nodelman [:alice] [:anode]]

Other than those mentioned in the first and second comments - so you'd have to sort through those list and see if there is anything in there that is worth while.  I might consider this all to be too vague, so I could see closing this as INCOMPLETE and recommending filing individual bugs to request specific new tests.

Comment 4

[alice nodelman [:alice] [:anode]]

Same as comment #3, but now I'm really going to close as INCOMPLETE.

Comment 5

[Chris Cooper [:coop] (he/him)]

Moving closed Future bugs into Release Engineering in preparation for removing the Future component.