Firefox OS/Performance/Boot Timing Automation: Difference between revisions

→‎Plan Outline: More links to actual implementation.
(→‎Plan Outline: More links to actual implementation.)
(→‎Plan Outline: More links to actual implementation.)
Line 15: Line 15:
#* Also capturing the timing of when we launch b2g proper
#* Also capturing the timing of when we launch b2g proper
#* File in JSON format to be compatible with the other tools.
#* File in JSON format to be compatible with the other tools.
# settings.js/shell.js generate a time stamp (that is stored in some standard property of the window) near its entrypoint. <br>
# settings.js/shell.js generate a time stamp (that is stored in some standard property of the window) near its entrypoint.
#* See {{bug|1058817}} and [https://bugzilla.mozilla.org/attachment.cgi?id=8479247&action=diff#a/b2g/chrome/content/settings.js_sec2 this changeset] for proposed implementation.
<!-- #* Is make test-perf's perfHelper available to observe?  What is this question asking? -->
<!-- #* Is make test-perf's perfHelper available to observe?  What is this question asking? -->
# System app (in chrome) records timing at some decided location (as in the prior step):
# System app (in chrome) records timing at some decided location (as in the prior step):
#* Do this right before iframe creation in shell.js ?
#* Do this right before iframe creation in shell.js ?
#* See {{bug|1058817}} and [https://bugzilla.mozilla.org/attachment.cgi?id=8479247&action=diff#a/b2g/chrome/content/shell.js_sec2 this changeset] for proposed implementation.
<!--#** why not IN the system proper?-->
<!--#** why not IN the system proper?-->
# System App:
# System App:
canmove, Confirmed users
261

edits