Program Management/Programs/Telemetry/Probe Implementation: Difference between revisions
< Program Management | Programs | Telemetry
Jump to navigation
Jump to search
DavidBolter (talk | contribs) |
DavidBolter (talk | contribs) |
||
| Line 18: | Line 18: | ||
===DOM - Johnny Stenback=== | ===DOM - Johnny Stenback=== | ||
===Graphics - Jeff Muizelaar=== | ===Graphics - Jeff Muizelaar=== | ||
The big one here is paint time. We should aim to never go above 16 ms. The paint time is the lower bound on any perceived responsiveness. Bug 694014. | The big one here is paint time. We should aim to never go above 16 ms. The paint time is the lower bound on any perceived responsiveness. {{Bug|694014}}. | ||
===JS - Dave Mandelin=== | ===JS - Dave Mandelin=== | ||
Revision as of 15:38, 12 October 2011
Questions to answer
The complete list of questions can be found in the Platform roadmap.
The current focus questions are:
- How fast can we load and render web pages?
- How fast can we start up?
- How fast can we react visually to people’s mouse movements and button presses?
Probes
Teams
A11y - David Bolter
Our Telemetry tracker is bug 648121. If we could get overall numbers for page load etc. I'd like to compare the numbers for when a11y happens to be instantiated (we already probe for a11y instantiation).
Audio/Video - Robert O'Callahan
DOM - Johnny Stenback
Graphics - Jeff Muizelaar
The big one here is paint time. We should aim to never go above 16 ms. The paint time is the lower bound on any perceived responsiveness. bug 694014.