Confirmed users
561
edits
Auto-tools/Projects/GoFaster/2011-07-06: Difference between revisions
Auto-tools/Projects/GoFaster/2011-07-06 (view source)
Revision as of 20:14, 6 July 2011
, 6 July 2011→Discussion Points
(Created page with "= Many Projects, all Complementary = * MozBase * Special Powers * Going Faster = MozBase = * [[Auto-tools/Projects/MozBase| Project to refactor base libraries of test harnesses ...") |
|||
| Line 36: | Line 36: | ||
* How to best work together without stepping on toes? | * How to best work together without stepping on toes? | ||
* How can we monitor test harness performance so we know if we check in something that blows our gains? | * How can we monitor test harness performance so we know if we check in something that blows our gains? | ||
= Meeting Notes = | |||
== Special powers == | |||
*Cleanup harness | |||
**Many tools touched (unit tests, talos etc.) | |||
*Moving tests to the right harnesses | |||
*Update all the tests | |||
**need to contact other devs to fix their tests | |||
*mochitest monitoring to see if Special Powers will slow us down, need to check end to end time | |||
==Going Faster== | |||
*Getting rid of packed.js would shave ~5 mins from test run of mochitests. We only use a small bit of it, we don't need to load all. | |||
*Write a Mochitest profiling test suite so we can run to profile our progress. | |||
*Is our JS webserver a bottleneck? Should we switch to another server? Suggestions: nginx, lighttpd, etc. | |||
**Profiling: Run a suite that doesn't use .sjs or special content headers and test against current httpd.js server and the server we're testing | |||
*There should be profilers for each harness, but start with mochitests. | |||
*Should we combine some Mochitest test files into one huge generated test instead of a directory of many test files so we can load the overhead once? | |||