Confirmed users
1,927
edits
Auto-tools/Projects/peptest: Difference between revisions
Jump to navigation
Jump to search
→Further Work
(Moved overview, usage, test format, and API reference to MDN) |
|||
| Line 11: | Line 11: | ||
=== Automatic reports === | === Automatic reports === | ||
{{bug|737886}} | {{bug|737886}} Set up reporting when significant deviations occur in buildbot's peptest results. Since we can't develop a simple pass/fail result, developers will have to rely on these reports to determine when responsiveness has gotten worse (or better). | ||
=== Telemetry histograms === | === Telemetry histograms === | ||
Capturing telemetry information would be useful in diagnosing causes of responsiveness. Results would be available after running a test, and by clicking through on the stats UI. | {{bug|740462}} Capturing telemetry information would be useful in diagnosing causes of responsiveness. Results would be available after running a test, and by clicking through on the stats UI. | ||
=== Integration with SPS === | === Integration with SPS === | ||
For each function wrapped in a performAction() call, we should enable the profiler, so we can tell where each action spent its time. We can use [https://developer.mozilla.org/en/Performance/Profiling_with_the_Built-in_Profiler SPS] to this end | {{bug|706847}} For each function wrapped in a performAction() call, we should enable the profiler, so we can tell where each action spent its time. We can use [https://developer.mozilla.org/en/Performance/Profiling_with_the_Built-in_Profiler SPS] to this end. | ||
=== Mozmill e10s === | === Mozmill e10s === | ||