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

no edit summary
mNo edit summary
No edit summary
Line 34: Line 34:
<code>make test-perf</code> will consume the file, and all these events to give back meaningful data.
<code>make test-perf</code> will consume the file, and all these events to give back meaningful data.
In the pre-gecko timing one of the data points will be a pair of both "uptime" and "epoch time". Using this, we can calculate the time of boot in terms of epoch time, which is more compatible with times we have access to in the higher levels of the stack. Then, for each "created" event the current time will be recorded, etc. There may need to be additional handling for getting compatible times from the <code>moz-*</code> events.
In the pre-gecko timing one of the data points will be a pair of both "uptime" and "epoch time". Using this, we can calculate the time of boot in terms of epoch time, which is more compatible with times we have access to in the higher levels of the stack. Then, for each "created" event the current time will be recorded, etc. There may need to be additional handling for getting compatible times from the <code>moz-*</code> events.
<!--Also might need to special case shell.js piece, to include its own timing information in the event fired-->
<!--Might not need to change make test-perf timing with the help of Navigation.start but basically the problem is that it uses Windows.performance.now() for its timings which gives us no context w.r.t the early timing information-->
<!--Might not need to change make test-perf timing with the help of Navigation.start but basically the problem is that it uses Windows.performance.now() for its timings which gives us no context w.r.t the early timing information-->


Confirmed users
125

edits