Closed Bug 386668 Opened 16 years ago Closed 14 years ago

Add additional performance test suites to talos


(Release Engineering :: General, defect)

Not set


(Not tracked)



(Reporter: mtschrep, Unassigned)



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

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.
Some more sources of benchmarks:,1697,2152778,00.asp

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

Some synthetic JS benchmarks.  Try/Catch benchmark is questionable but the math, DOM, Array, and String functions look reasonable:
Depends on: talos-generalize
Component: Testing → Release Engineering: Future
Product: Core →
QA Contact: testing → release
Version: unspecified → other
Found during triage. 

Alice: are there some specific test suites here that we should add to Talos?
OS: Windows Vista → All
Hardware: x86 → All
Summary: Add additional performance tests to talos → Add additional performance test suites to talos
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.
Same as comment #3, but now I'm really going to close as INCOMPLETE.
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: → Release Engineering
You need to log in before you can comment on or make changes to this bug.